App Often Crashing and Notification Failure since v1.8.22.

[G-i-o]

• I have searched for existing issues that may be the same as or related to mine.

Please complete the following information:

Device: Google Pixel 3a
Android Version: Lineage v21 (Android 14).
Orgzly Revived Version: 1.8.22
Repository type(s) used (e.g. directory, Dropbox, WebDAV): F-Droid

Since v1.8.22 the app seems to be crashing frequently. Moreover, and this may be a consequence, when the app isn't opened in the background, the notification don't work and the widget does not get updated.

The app has the notification permissions allowed.

The previous version, v1.8.21, was not having this issue.

Thank Your for keeping up the good work. 🙏

[amberin]

Thank you for reporting. This sounds really bad. We seem to be having multiple permission issues on Lineage, see also #200.

I'm afraid it's really hard to troubleshoot without a virtual device running Lineage, and I cannot build an image myself because I only have a laptop to work with.

The biggest change in v1.8.22 is that we're targeting Android 13, which entails a lot of changes in permission handling. This is probably related to these issues.

[amberin]

If you can find a certain way to reproduce a crash or notification failure, that would be highly valuable.

[alexvorobiev]

I am having the same issue on Pixel 8 pro - the app is unusable. It either doesn't respond or crashes. I will be reinstalling the previous version.

[amberin]

@alexvorobiev wrote:

I am having the same issue on Pixel 8 pro - the app is unusable. It either doesn't respond or crashes. I will be reinstalling the previous version.

Please provide as much information as possible to help identify the bug. Are you also running LineageOS, or the Pixel's stock Android? In what situations does the app crash or stop responding?

[amberin]

FWIW, I have a Sony Xperia 10 II with LineageOS 20 (Android 13), and v1.8.22 works for me there.

There is something wrong with requesting permissions, though -- I never got the "allow alarms & reminders" prompt, which is supposed to show when syncing if the permission has not been granted. I'll look into it. Nope, I was confusing the behavior in Android 13 and 14. In 14, apps need to be explicitly granted the "alarms & reminders" permission by the user, but this is 13, so it's already granted upon install (if present in the manifest). I wish I could test on Lineage v21, but unfortunately, there is no build for my device.

If I sync books with content which should lead to notifications being scheduled, I get a snack bar saying the notifications permission is missing, as I should. The same thing happens if I set a scheduled or deadline exact time, and save a book.

Are any of these situations when you experience crashes? I.e. during sync or when updating a note with reminder information?

[alexvorobiev]

@alexvorobiev wrote:

I am having the same issue on Pixel 8 pro - the app is unusable. It either doesn't respond or crashes. I will be reinstalling the previous version.

Please provide as much information as possible to help identify the bug. Are you also running LineageOS, or the Pixel's stock Android? In what situations does the app crash or stop responding?

I am on the stock Android 14. The app stops responding when I try to click on the checkboxes next to the Todo items.

[n-hebert]

Adding my report that my Pixel 7 Pro with stock Android 14 is seeing crashes and I can no longer receive timely notifications on the latest Orgzly 1.8.22. They mostly arrive delayed, when I open the app manually.

[amberin]

I published v1.8.23 yesterday, it should be on Fdroid within a few days. Please try it and see if the issues remain.

[n-hebert]

1.8.23 seems better. Notification loss was always a bit random, so I can't say for 100% but I'm optimistic.

[G-i-o]

Yes, 1.8.23 seems to be working now as it used to for me as well.

[licaon-kter]

/close this then