You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally, calling the completion handler twice might not be an issue. However, when combined with FirebaseMessaging/GoogleUtilities’ swizzled code (see this exception trigger), it provokes an exception because GoogleUtilities does not expect multiple invocations.
fetchCompletionHandler should be called exactly once.
Actual Incorrect Behavior
It is called twice—once via the superclass’s didReceiveRemoteNotification:fetchCompletionHandler and once within BrazeKit—triggering an exception in FirebaseMessaging/GoogleUtilities.
The text was updated successfully, but these errors were encountered:
Braze Unity SDK Version
7.1.0
Steps To Reproduce
The fetchCompletionHandler in AppboyAppDelegate is invoked twice:
• First Call: Link to first occurrence
• Second Call: Link to second occurrence
Normally, calling the completion handler twice might not be an issue. However, when combined with FirebaseMessaging/GoogleUtilities’ swizzled code (see this exception trigger), it provokes an exception because GoogleUtilities does not expect multiple invocations.
For reference, here’s the crash stack trace:
Expected Behavior
fetchCompletionHandler should be called exactly once.
Actual Incorrect Behavior
It is called twice—once via the superclass’s didReceiveRemoteNotification:fetchCompletionHandler and once within BrazeKit—triggering an exception in FirebaseMessaging/GoogleUtilities.
The text was updated successfully, but these errors were encountered: