Avoid double callback of fetchCompletionHandler in didReceiveRemoteNotification #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tification Use a callbackGroup to wait for all fetchCompletionHandler callbacks and aggregate result, then call original completion handler one single time
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses issue #107 by preventing a double invocation of fetchCompletionHandler in didReceiveRemoteNotification.
Currently, the handler is called twice—once by the superclass (UnityAppController) and once in BrazeKit—which can lead to crashes (notably with GoogleUtilities). The fix introduces a localCompletionHandler and uses a dispatch group to wait for all callbacks before aggregating their results and calling the original completion handler exactly once.