[flutter_local_notifications] Added ability to bind to ForegroundService #2677
+149
−2
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
MaikuB
requested changes
Oct 6, 2025
Owner
MaikuB
left a comment
MaikuB
left a comment
There was a problem hiding this comment.
Thanks for the PR and apologies for delay on getting back on this. I left some comments on the PR with some requested/proposed changes. Let me know what you think and happy to discuss further
| ⚠️ For Android 8.0+, sounds and vibrations are associated with notification channels and can only be configured when they are first created. Showing/scheduling a notification will create a channel with the specified id if it doesn't exist already. If another notification specifies the same channel id but tries to specify another sound or vibration pattern then nothing occurs. | ||
| ### Bind ForegroundService to your FlutterActivity |
Owner
There was a problem hiding this comment.
The table of contents is missing an update that allows for jumping to this section
| ### Bind ForegroundService to your FlutterActivity | ||
| In your activity (e.g., `MainActivity.kt`), set up a broadcast receiver and a `ServiceConnection` to manage binding and unbinding. This is not required to use a `ForegroundService` but it will decrease the likelyhood of your activity being [killed or frozen by the OS while the activity is in the background](https://source.android.com/docs/core/perf/cached-apps-freezer#handling-custom-features): |
Owner
There was a problem hiding this comment.
Can this start off by saying it's optional and only applicable for apps using foreground services? Thinking behind this is some readers may not pick this up or know enough about Android development to realise
| Intent intent = new Intent(applicationContext, ForegroundService.class); | ||
| intent.putExtra(ForegroundServiceStartParameter.EXTRA, parameter); | ||
| ContextCompat.startForegroundService(applicationContext, intent); | ||
| applicationContext.sendBroadcast(new Intent("com.dexterous.flutterlocalnotifications.FOREGROUND_SERVICE_STARTED") |
Owner
There was a problem hiding this comment.
Let me know what you think but I believe it's best to do the following
- add additional folders that so that
com.dexterous.flutterlocalnotifications.intent.actionnamespace exists. This is to follow convention of having the strings behind a namespace where last segment hasactionlike other actions e.g.android.intent.action.<...>andhtc.com.intent.action.<...> - create a class within the
action(i.e.com.dexterous.flutterlocalnotifications.intent.actionnamespace) that holds public static strings forcom.dexterous.flutterlocalnotifications.action.FOREGROUND_SERVICE_STARTEDandcom.dexterous.flutterlocalnotifications.action.FOREGROUND_SERVICE_STOPPED. This to allow developers an easier way to reference the strings through the plugin. The best name I can come up with for the class isFlutterLocalNotificationsPluginIntent. It'd be similar to how developers can referenceIntent.ACTION_VIEW_LOCUS. In this case, they can referenceFlutterLocalNotificationsPluginIntent.FOREGROUND_SERVICE_STARTEDandFlutterLocalNotificationsPluginIntent.FOREGROUND_SERVICE_STOPPED
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds the necessary components to the ForegroundService components to allow developers to listen for a broadcast and bind to the ForegroundService when it is created. This will promote the activity and reduce the likelihood of it being frozen or killed due to resource constraints by the OS. Updated the README and example app to show how it can be integrated if chosen.
Tested with the example app on Android 9 & 15