-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXC_BAD_ACCESS OSInAppMessageViewController (bottomAnchor > centerXAnchor ... Attempted to dereference garbage pointer 0x38.) #1304
Comments
I am also getting this error. It happens when receiving any in-app message to iOS via OneSignal. I am using react-native-onesignal with the expo managed workflow, set up using onesignal-expo-plugin, built using expo's EAS service.
Android in-app messages work absolutely fine. |
Howdy, It's hard to debug segmentation faults. Clearly, this is a lower level native issue that if anything would be caused by a bug on the native SDK side. What seems to be happening is a variable has gone out of memory and is trying to be accessed. However, it's quite possible this is unrelated to OneSignal at all. It's possible for another process to overwrite a bit of memory OneSignal is using (heap corruption). Question: can this be consistently reproduced and how widespread is the impact if in production (crashlytics or similar reporting info would be helpful)? |
I have the same issue. It happens consistently when opening the app and the In-App Message is launched. When I mute the In-App Message the error does not happen / issue. I have error logs in Sentry if that's of any use. |
@kierandesmond If you can share the logs with support@onesignal.com we would be happy to take a look. |
Anyone have a reply to my comment above? |
Closing due to inactivity |
Description:
The crash happens on first app launch if an inapp message is scheduled to appear on launch (such as the predefined App Store Rating message). It is reproducible with react-native-onesignal but not when integrating just the native iOS SDK. In our production app, this often happens on every launch. In an empty project we setup for testing the issue, it happens once on first launch, then almost never on subsequent launches. This does not happen when debugging, only in release builds.
Environment
Testing on iOS 15, iOS 14.6
Steps to Reproduce Issue:
react-native-onesignal
using yarn into your projectAnything else:
Reviewed two similar issues where the crash also relates to constraints and occurs in OSInappMessageViewController. However, messaging is not the same and it appears these issues have already been fixed:
The text was updated successfully, but these errors were encountered: