Andrew Engelbrecht

I should note that I tried wiping and uninstalling the app, and the crashing stopped. So hopefully I can reproduce the bug on a new build the next time GrapheneOS...

I tested an older version of my app with the app optimization, and persistent crashing returned. Sideloading an updated app with the recommended change, using `START_REDELIVER_INTENT`, among other changes, caused...

Yes, I can test out `START_NOT_STICKY` at some point and see if it works for me. My hunch is that this will not be something that my app needs, if...

Using `START_NOT_STICKY` does not lead to any crashes for me after apps are optimized in GrapheneOS and then restarted automatically.

Thanks for the pointer. : ) I think that in this case, Flutter Local Notifications is probably not passing all metadata it has to the Java compat library, so while...

I think what's needed is some kind of mapping between notification IDs and whether they were created with a parameter that marked them as needing cleanup on app termination. That's...

I'm not sure when, but I'll take a look and see what I can do.

> Can you try using the same ID you did in `createForegroundService` to call `show()` the standard way, and confirm that it changes your notification? I can confirm that works....

I'm not really sure how it is handled on desktop Linux.. and it may vary according to the notification daemons used by various desktop environments. I could look into this...

I was getting this error on Tumbleweed with both `asdf` and `mise`, a similar tool. Make sure that you run the following command to install build tools before trying to...