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
When invoking Notify(callback, options) - the synchronous method - in an iOS app on the main thread, the app will crash when the user taps the notification. This happens only in the release build, the debug build behaves as expected. The async Notify(options) method works without problems in both debug and release builds.
When connecting the Xcode debugger to the running release build and then crash the app by tapping a notification, the debugger indicates that EXC_BAD_ACCESS occurs in System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.InvokeMoveNext() (InvokeMoveNext.cs:1089).
I have not tested this on Android as I was in a bit of a rush to fix the bug for a new release.
The text was updated successfully, but these errors were encountered:
When invoking Notify(callback, options) - the synchronous method - in an iOS app on the main thread, the app will crash when the user taps the notification. This happens only in the release build, the debug build behaves as expected. The async Notify(options) method works without problems in both debug and release builds.
When connecting the Xcode debugger to the running release build and then crash the app by tapping a notification, the debugger indicates that EXC_BAD_ACCESS occurs in System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.InvokeMoveNext() (InvokeMoveNext.cs:1089).
I have not tested this on Android as I was in a bit of a rush to fix the bug for a new release.
The text was updated successfully, but these errors were encountered: