refactor(messaging, android): removed unsafe & deprecated API. E.g. LocalBroadcastManager
replaced by LiveData
#11659
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.
Description
This effects the
refreshToken
&onMessage
API. For completeness, I also tested theonMessageOpenedApp
& theonBackgroundMessage
handler. They all worked as intended.List of changes made:
LocalBroadcastManager
API in favour of the recommendedLiveData
API.sendMessage()
as the underlying android APIsend()
is deprecated and will be decommissioned in June 2024.Related Issues
Addressed some messaging warnings for this issue: #8073
Still need to return and work on the JobIntentService which has a number of deprecated API.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?