fix(messaging, iOS): scope iOS 18 duplicate notification workaround to iOS 18.0 only #17932
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
PR #13572 introduced a duplicate notification check to work around an iOS 18.0 OS bug where the same notification is delivered twice. However, this check was applied to all iOS versions and used
notification.request.identifierfor comparison, which caused legitimate notification updates usingapns-collapse-idto be suppressed.When multiple notifications share the same
apns-collapse-id, iOS maps them to the samerequest.identifier, causing only the first notification to triggerFirebaseMessaging.onMessage.listen- subsequent updates were incorrectly filtered as duplicates.Solution
Related Issues
Fixes #17923
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.yamland 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?