-
-
Notifications
You must be signed in to change notification settings - Fork 324
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
iOS crash on launch after upgrade to 5.3.0 #2956
Comments
Hi, Do you see any other errors, running the app directly from Xcode could help to see more iOS logs and stack trace of the crash. Just for context, I'm linking the original issue and the reason why you are upgrading. |
@bpeltonc Did you manage to get your project working? Or still, facing the same issue? |
@krystofwoldrich Unfortunately, the project I have inherited has some bigger build issues that prevent me from building in XCode (I build using 'react-native' and fastlane cli tools only). It might be best to table this issue until I get my project fully upgraded and these larger issues sorted out. |
@bpeltonc Okay, thank you for the update, I will close this for now, and when you get back to it, comment here and we can reopen it. |
@krystofwoldrich I have confirmed there are no Sentry pods in my |
We have found out what the issue was, and here is a fix. #2980 When it's released Sentry will be in the Pods. If you want to use the v5 now you can link RNSentry manually. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.3.0
react-native
version: 0.66.3Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
Configuration:
(
@sentry/react-native
)I have following issue:
After following the migration guide to upgrade my previous 3.1.x version to 5.3.0, iOS builds are crashing both in debug and release builds. Android is working fine, it appears. With a debug build, I get a log in my console as follows: "Native Client is not available, can't start on native." I tried including
enableNative: false
in my config, but still got the same result.Steps to reproduce:
Actual result:
Crash on app start
Expected result:
App works with no crash
The text was updated successfully, but these errors were encountered: