Fix NotificationResponse race condition #3740
Merged
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.
Details
For a while, the callback for the
NotificationResponse
event (i.e: when a push notification is tapped) was usually not being executed. The previous code falsely assumed that theNotificationResponse
callback would happen while the app was still in the background, because it is when the event occurs. It did rarely happen this way, because there was a race condition in play between these two responses to this event:The native OS response is almost always faster, so by the time the JS callback executes, the app is in the foreground and we skipped the callback. Instead, we'll only skip the callback for
PushReceived
events that happen when the app is in the foreground.Fixed Issues
Fixes (partial) https://github.com/Expensify/Expensify/issues/158830
Tests / QA Steps
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
RPReplay_Final1624493296.MP4
Android