Instantly crashes on login

[jaymehta-g]

** Jerboa Version **
0.0.33

Describe the bug
Galaxy s10+

Lemmy instance is lemmy.blahaj.zone

App instantly crashes on login, gives error "value of java.lang.String cannot be converted..." Rest of error is cut off

To Reproduce
Accounts menu > Add Account, then log in

[twizmwazin]

We should probably implement some sort of top level exception handling that allows the user to submit a bug report directly from the app to make it easier to get a full backtrace. If you can get the full backtrace from logcat that'd be great.

[Flouzr]

I believe I was able to capture the error in the attached logs. I've uploaded them to pastebin here.

[Luunae]

I'm getting this error too, across large portions of the app. Feels like mostly when things fail to load for some reason.

Unsure how to get logs.

Galaxy Z Flip 4
Jerboa 0.0.32

[MV-GH]

I believe I was able to capture the error in the attached logs. I've uploaded them to pastebin here.

Can you get the logs of the error in a debug build? due to obfuscation and minification the stacktrace isn't very usefull

[Nawor3565]

I believe I was able to capture the error in the attached logs. I've uploaded them to pastebin here.

Can you get the logs of the error in a debug build? due to obfuscation and minification the stacktrace isn't very usefull

Sorry if this is a dumb question, but would that mean installing one of the alpha .apks from GitHub, or would I need to compile the app myself? I'm having the same issue (also using lemmy.blahaj.zone, funny enough) and I'd like to help address the bug in whatever way I can.

[MV-GH]

I believe I was able to capture the error in the attached logs. I've uploaded them to pastebin here.

Can you get the logs of the error in a debug build? due to obfuscation and minification the stacktrace isn't very usefull

Sorry if this is a dumb question, but would that mean installing one of the alpha .apks from GitHub, or would I need to compile the app myself? I'm having the same issue (also using lemmy.blahaj.zone, funny enough) and I'd like to help address the bug in whatever way I can.

You would need to compile the app yourself, if that is not possible i can drop a debug apk build here the comments

[Nawor3565]

If you could drop a debug apk, that would be great!

…

On Tue, Jun 13, 2023, 9:57 AM Maarten Vercruysse ***@***.***> wrote: I believe I was able to capture the error in the attached logs. I've uploaded them to pastebin here <https://pastebin.com/QdTg0gkT>. Can you get the logs of the error in a debug build? due to obfuscation and minification the stacktrace isn't very usefull Sorry if this is a dumb question, but would that mean installing one of the alpha .apks from GitHub, or would I need to compile the app myself? I'm having the same issue (also using lemmy.blahaj.zone, funny enough) and I'd like to help address the bug in whatever way I can. You would need to compile the app yourself, if that is not possible i can drop a debug apk build here the comments — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEW57UFQMWQAG4UA4CRRHY3XLBWTDANCNFSM6AAAAAAZCQZZ7Q> . You are receiving this because you commented.Message ID: ***@***.***>

[MV-GH]

jerboa-debug.zip
Here, it will give you some trouble to install it but it should allow it (due to it not being signed)

[dessalines]

I'm fairly positive I fixed that padding bug in calculateCommentOffset, that's already included in 0.0.33, so this must be a different one.

[Nawor3565]

Weirdly enough, I am suddenly no longer having this issue on either the developer version *or* the stable 0.0.33 release from the Play Store. I wonder if it was caused by some bug with lemmy.blahaj.zone that they just fixed EDIT: it appears that downvotes were somehow disabled on the instance until about 12 hours ago. Maybe this is related?

…

On Tue, Jun 13, 2023, 11:06 AM Dessalines ***@***.***> wrote: I'm fairly positive I fixed that padding bug in calculateCommentOffset, that's already included in 0.0.33, so this must be a different one. — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEW57UDO6LWO3TOJ6EC4IP3XLB6VPANCNFSM6AAAAAAZCQZZ7Q> . You are receiving this because you commented.Message ID: ***@***.***>

[jaymehta-g]

Weirdly enough, I am suddenly no longer having this issue on either the developer version or the stable 0.0.33 release from the Play Store. I wonder if it was caused by some bug with lemmy.blahaj.zone that they just fixed EDIT: it appears that downvotes were somehow disabled on the instance until about 12 hours ago. Maybe this is related?
…
On Tue, Jun 13, 2023, 11:06 AM Dessalines @.> wrote: I'm fairly positive I fixed that padding bug in calculateCommentOffset, that's already included in 0.0.33, so this must be a different one. — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEW57UDO6LWO3TOJ6EC4IP3XLB6VPANCNFSM6AAAAAAZCQZZ7Q . You are receiving this because you commented.Message ID: @.>

Same here it works just fine for me.

[noloman]

I couldn't reproduce it anymore; it just works for me

[MV-GH]

Strange, definitely should be looked at, but we can only speculate at this point. maybe lemmy gave timeout response which couldn't be converted and isn't properly handled like the others that caused crash?

[jaymehta-g]

I still get this error very often, seemingly at random, but it doesn't lead to a crash. Usually when something fails to load

[MV-GH]

This error?

Yeah i think its when jerboa receives a timeout instead of a proper response we could handle it better and just keep the old posts for now and retry