search

beeminder / beedroid

This is a repository to keep track of issues with the Beeminder Android app
6 stars 0 forks source link

Tracking issue for Notification JobIntentService #76

Closed adamwolf closed 1 year ago

adamwolf commented 5 years ago

I had swapped the IntentService out for a JobIntentService, and it works great for some folks, and not for others. If it works great for you, you can often open the app, and then swipe it closed, then open it again, and it will not work then. "Not working" means you are successfully enqueueing work on the NotificationService, but it is not being handled after the first time. When it's working, it handles the queue no matter what.

I found some folks online who had similar issues.

https://stackoverflow.com/a/55933063

We are working around it right now in a different way in a test, but I suspect we'll be returning to this bug soon enough. The code is on tag 2.10.3.

adamwolf commented 5 years ago

When I get back to this, I can pull the AlarmReceiver back in, but I need to add the new intents like Force Zeno to the filter in the manifest.

adamwolf commented 5 years ago

When I get back to this, take a look at GlobalData and see if we are enqueueing work "too fast" and breaking the lifecycle at the startup.

adamwolf commented 1 year ago

When we use push notifications for alerts (#126), we won't have a Job Intent Service.

adamwolf commented 1 year ago

Fixed as of Beedroid 5.