Crash on startup when the instance isnt available #59

New Issue

davidoskky · 2022-09-24T10:05:30Z

davidoskky commented

2022-09-24 10:05:30 +00:00

F-Droid version.
If the selfoss instance where you successfully logged in goes down, the application crashes on startup.
It would be better to provide an error message and go back to the login screen, because otherwise the user will be forced to clear cache in order to change the login information.

Logcat:
The application performs a 3 api calls to items and one to tags; all of these return a 404 error and then outputs this before crashing:

channel 'cb644e1 bou.amine.apps.readerforselfossv2.android/bou.amine.apps.readerforselfossv2.android.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed!

I'm confused as to why the application is making 3 api calls to items rather than just one.

F-Droid version. If the selfoss instance where you successfully logged in goes down, the application crashes on startup. It would be better to provide an error message and go back to the login screen, because otherwise the user will be forced to clear cache in order to change the login information. Logcat: The application performs a 3 api calls to items and one to tags; all of these return a 404 error and then outputs this before crashing: ``` channel 'cb644e1 bou.amine.apps.readerforselfossv2.android/bou.amine.apps.readerforselfossv2.android.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed! ``` I'm confused as to why the application is making 3 api calls to items rather than just one.

davidoskky commented

2022-09-24 10:08:38 +00:00

Overall, this version feels a bit more buggy than the old one.
I have experienced several crashes while using it, this is the only one I was able to reproduce easily and catch a logcat.

It would be nice to provide one of those error collecting services, so that we can get stacktraces of errors experienced by normal users who won't come here and provide the error message.

Overall, this version feels a bit more buggy than the old one. I have experienced several crashes while using it, this is the only one I was able to reproduce easily and catch a logcat. It would be nice to provide one of those error collecting services, so that we can get stacktraces of errors experienced by normal users who won't come here and provide the error message.

AmineB changed title from ~~Crash on startup~~ to Crash on startup when the instance isnt available

2022-09-24 11:19:12 +00:00

AmineB added the

Priority = Normal

Type = Bug

labels 2022-09-24 11:39:39 +00:00

AmineB added this to the Bugfixes milestone 2022-09-24 11:39:45 +00:00

AmineB added this to the Dev project 2022-09-24 11:39:48 +00:00

AmineB self-assigned this 2022-09-24 11:39:54 +00:00

AmineB referenced this issue

2022-09-24 11:43:37 +00:00

Crash report collecting ? #60