[5.0.0] Support multiple IAM + Notification Lifecycle Listeners #1278
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
One Line Summary
Support multiple IAM Lifecycle Listeners + Notification Foreground Lifecycle Listeners.
Details
Motivation
No API change, but under the hood, support adding multiple listeners that remained a TODO after these two PRs:
Scope
Letting app developers add and remove multiple listeners. When there are multiple notification foreground listeners, essentially first one wins. The first listener to call
preventDefault
anddisplay
will trigger these events.In addition, added
jsonRepresentation
to IAM lifecycle events[event jsonRepresentation]
OSInAppMessage
, however sinceOSInAppMessageInternal
is a subclass ofOSInAppMessage
, we end up exposing the internal properties. Therefore, I renamed the method onOSInAppMessageInternal
tojsonRepresentationInternal
, which is used for debugging.Testing
Manual testing
Tested on iPhone 13 device on iOS version 16.5
display
andpreventDefault
in various configurations.Affected code checklist
Checklist
Overview
Testing
Final pass
This change is