This repository was archived by the owner on Feb 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
android_alarm_manager background execution bug fixes #1129
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jan 28, 2019
zanderso
reviewed
Jan 28, 2019
...alarm_manager/android/src/main/java/io/flutter/plugins/androidalarmmanager/AlarmService.java
Outdated
Show resolved
Hide resolved
.../android/src/main/java/io/flutter/plugins/androidalarmmanager/AndroidAlarmManagerPlugin.java
Show resolved
Hide resolved
zanderso
approved these changes
Jan 29, 2019
* Updated android_alarm_manager to fix issues with "background start not allowed" when attempting to start AlarmService while backgrounded. * Switched to using a combination of BroadcastReceiver and JobIntentService from using a Service (launching a Service from an alarm Intent causes the "Background start not allowed" on Android 8+) * Alarm events received before the AlarmService isolate is finished initializing are now queued and processed once the isolate is initialized. * Updated CHANGELOG.md and README.md with new setup steps. * Bumped version to 0.4.0. Fixes #26846.
ce8d87e to
c9b81dd
Compare
4e6a87d to
c9b81dd
Compare
Contributor
|
cc @mklim |
andreidiaconu
pushed a commit
to andreidiaconu/plugins
that referenced
this pull request
Feb 17, 2019
* android_alarm_manager background execution bug fixes * Updated android_alarm_manager to fix issues with "background start not allowed" when attempting to start AlarmService while backgrounded. * Switched to using a combination of BroadcastReceiver and JobIntentService from using a Service (launching a Service from an alarm Intent causes the "Background start not allowed" on Android 8+) * Alarm events received before the AlarmService isolate is finished initializing are now queued and processed once the isolate is initialized. * Updated CHANGELOG.md and README.md with new setup steps. * Bumped version to 0.4.0. Fixes #26846.
andreidiaconu
added a commit
to andreidiaconu/plugins
that referenced
this pull request
Feb 17, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated android_alarm_manager to fix issues with "background start not
allowed" when attempting to start AlarmService while backgrounded.
JobIntentService from using a Service (launching a Service from an
alarm Intent causes the "Background start not allowed" on Android 8+)
Alarm events received before the AlarmService isolate is finished
initializing are now queued and processed once the isolate is
initialized.
Updated CHANGELOG.md and README.md with new setup steps.
Bumped version to 0.4.0.
Fixes flutter/flutter#26846.