-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Crash when selecting new articles section #448
Comments
Can you please try a fresh installation? For some reason it seems like some devices did not get their database updated and don't have the column "score" so it crashes when selecting articles by score for the fresh feed. The invalid installation info is because the app is signed with a different key, f-droid ships their own builds and since they often are way behind Iwas tired of getting so many mails for old bugsthat were fixed half a year ago. So I decided to enable bug reports by mail only for my own builds and only for the newest one or two versions. |
If I install 1.96.3 fresh, it crashes again. If I install 1.96.1 or 1.96.2 fresh from f-droid it works. If I then upgrade to 1.96.3, it keeps working. Maybe something with creating the DB on new installs is broken in 1.96.3? |
Same issue with new install 1.96.3 and 1.96.4 from Google. |
Selecting "reset database" from Settings does not help with this issue. However, I can confirm that a fresh install of 1.96.2 from FDroid makes this issue go away, and it stays absent after upgrading to 1.96.3. Subsequently uninstalling 1.96.3 from FDroid and then installing 1.96.4 from Play Store brings it back though. I notice that finishing the installation takes a long time. At that point, logcat has
|
Release is due tomorrow, hope this fixes it. |
With version 1.96.3 from f-droid on a device with lineageOS 17.1 (based on android 10) , whenever I select the top level "neue Artikel" (german, not sure what the english text it) section, ttrss-reader crashes with:
Except for the new articles section, it seems to work fine.
Any idea, how to find out why it thinks "Error reporting disabled, invalid installation"?
On a different device running on grapheneos (based on aosp 11) with the same ttrss-reader version using the same ttrss server and account, it works fine.
The text was updated successfully, but these errors were encountered: