[MOB-3588] Add PendingIntent.FLAG_UPDATE_CURRENT to action button intents #390
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.
🔹 Jira Ticket(s) if any
✏️ Description
Without it, if the hashCodes matches a button from one of the previous notifications, the pending intent won't be updated, and it may perform an action from the old message.
The root of the issue is that we generate PendingIntents with a
requestCodethat is not guaranteed to be unique per message. As a result, ifrequestCodecollides with a pendingIntent created by an older message (potentially from another template entirely), it will reuse the PendingIntent from the old notification. AddingPendingIntent.FLAG_UPDATE_CURRENTshould make it update the PendingIntent ifrequestCodes collide.