-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jerboa crashes when post contains an invalid date format (double Z at the end) #1230
Comments
If it doesn't always crash, go to settings > about > crash logs But those will be gone if u deleted appdata In the issue bug creation menu at the bottom there is entire guide to get the logs. Which would really need to understand the cause. |
Btw another thing, when it crashes on startup can you turn off internet. And see if it still crashes if not. Definitely get crash logs from the crashlogs section in About. |
I submitted this report on mobile so didn't see the helpful text there :( Thanks GitHub. I'll give adb a go later. Thanks :) |
Oh that's much easier. ...lol Looks like a double zulu on the date
java.time.format.DateTimeParseException: Text '2023-09-11T20:41:58.396046ZZ' could not be parsed, unparsed text found at index 27
Name: main
Report ID: e4497b36-bb41-444d-bbed-d9fc529abe9d
N/A
App name: Jerboa
N/A
|
Your custom instance what version is it running? is it running the latest main? Or just 0.18.4? The latest main already contains breaking changes for 0.19 which Jerboa does not support yet. |
Jerboa should definitely handle datetime parse failures better. But this is also backend issue, Lemmy should not be creating bad timezones. |
According to the UI
I'm not doing anything custom per-se I'm using the Either way, seems like a server-side issue |
If your are using the latest changes your are using the main with 0.19 changes. Could you report this at Lemmy that the main is creating badbly formatted datetimes |
Hi ! I just experienced a startup crash of Jerboa with the same exception (ie java.time.format.DateTimeParseException) and same callstack as mentioned in an earlier comment. What can I do as a user? Client: Jerboa 0.0.45 |
Just updated to Jerboa 0.0.46 via F-Droid. |
Which instance and what BE version does it say? This is very strange that it happens to a 0.18.4 version. In 0.19 that will come they made changes to the datetime which probably introduced the problem. I wasn't aware of this happening earlier. Right now as a user the only thing you can do delete appdata and do not login with that instance as it has problems. Make your admin aware of the potential problems. I will definitely look into making sure this won't crash Jerboa in the future but this won't be for a while. |
@MV-GH The instance is beehaw.org, and BE version is 0.18.4 at the time of testing (cf previous comments). I'll share this issue's link with admins. |
Thanks, I do have some questions for those admins. Are they running a custom version of lemmy 0.18.4? Have they cherrypicked any 0.19 changes into their BE? especially regarding time. Or maybe it's a existing issue that only recently started happening due to locale/ time changes |
Nvm this was entirely caused clientsided (By jerboa), Due to changes in timezone handling in 0.19. Which Jerboa did not support yet. Still strange that Beehaw was encountering these issues though. |
Edit: Crash logs further down: #1230 (comment)
I'll start by saying that I'm sorry this report is a bit sparse.. I don't know how to collect crash logs, especially seeing as the app stays running for maybe 200ms before crashing. Happy to provide some if someone points me at instructions.
So this started maybe a week ago? It only happens if I'm logged into my personal Lemmy instance. If I clear app data, it works fine until I again log in. I'm running the latest version (0.46-alpha from GitHub) and whatever the latest Lemmy container version is at the time of writing.
I'm not sure what else to try
The text was updated successfully, but these errors were encountered: