Hi,
I’ve been using Jerboa for some time, but one day it started saying “unable to verify JWT token” and I appeared to be not logged in any more.
So I removed the account and tried to re-add it. It crashes every time after entering my password.
Tried clearing the cache. No good.
Any ideas?
(Version 0.0.50 on a Samsung phone running Android 13)
settings -> about -> crash log
post crash here/my dms/github
Here we go. I stripped the device info because i wasn’t sure if any of it was identifying.
`` Stacktrace `` java.lang.IllegalStateException: You must either set a text or a view at com.android.internal.util.Preconditions.checkState(Preconditions.java:215) at android.widget.Toast.show(Toast.java:316) at com.jerboa.model.LoginViewModel$login$1.invokeSuspend(Unknown Source:637) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8) at kotlinx.coroutines.DispatchedTask.run(Unknown Source:109) at android.os.Handler.handleCallback(Handler.java:942) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:226) at android.os.Looper.loop(Looper.java:313) at android.app.ActivityThread.main(ActivityThread.java:8762) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@6ecbafe, Dispatchers.Main.immediate] `` END of stacktrace `` `` Thread info `` Name: main ID: 2 State: RUNNABLE Priority: 5 Thread group name: main Thread group parent: system Thread group active count: 35 Thread time: 0 hr 0 min, 3 sec `` END of thread info `` `` Exit reasons `` `` Exit reason #1 `` Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 15-11-2023 18:37:26 `` END of exit reason #1 `` `` Exit reason #2 `` Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 15-11-2023 18:36:51 `` END of exit reason #2 `` `` Exit reason #3 `` Description: AL_Kill : over 3 sec Importance: CACHED Reason: OTHER Timestamp: 14-11-2023 21:47:13 `` END of exit reason #3 `` `` END of exit reasons `` `` Application info `` App name: Jerboa Version code: 50 Version name: 0.0.50 Package name: com.jerboa Short package name: jerboa Flavor: N/A Signatures: nORRaWmGNmrBj18PL/p3svEr/s4= Is debuggable: No First installed: 05-07-2023 07:52:24 Last updated: 04-11-2023 00:18:37 Requested permissions: android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.READ_MEDIA_AUDIO, android.permission.READ_MEDIA_IMAGES, android.permission.READ_MEDIA_VIDEO, com.jerboa.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION Default prefs: N/A Default prefs: N/A `` END of Application info `` `` Currently running foreground/background processes `` N/A `` END of running foreground/background processes info ``
If it’s the account you are using rn, it is because, 0.19 is not supported yet by Jerboa
(It’s not fully released)
You mean sdf runs a too new lemmy?
Yes, the latest release of lemmy is 0.18.5
Right. Thanks.
It’d be good if Jerboa gave a descriptive error message onstead of outright crashing.
That’s already been fixed, and will be part of 0.0.51
Great! Thanks.
I have this issue currently because Lemmy.ml is on a newer version. Didn’t realize authentication would break
I just had to move to a different Lemmy app.
deleted by creator