-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
Unsymbolicated sentry stack traces #4118
Comments
Hi and thank you for opening this issue! |
The android native release happens through fastlane: bundle exec fastlane android release_playstore
# upload sentry sourcemaps
export SENTRY_PROPERTIES=./android/sentry.properties
npx react-native bundle --dev false --platform android --entry-file index.js --bundle-output index.android.bundle --sourcemap-output index.android.bundle.map
node_modules/@sentry/cli/bin/sentry-cli releases files $VERSION-$JSVERSION upload-sourcemaps --strip-prefix . --rewrite index.android.bundle index.android.bundle.map --dist $VERSIONCODE Here are the contents of lane:
iOS native release also happens through fastlane bundle exec fastlane ios build_appstore
bundle exec fastlane ios release_appstore
# upload sentry stuff
export SENTRY_PROPERTIES=./ios/sentry.properties
npx react-native bundle --dev false --platform ios --entry-file index.js --bundle-output main.jsbundle --sourcemap-output main.jsbundle.map
node_modules/@sentry/cli/bin/sentry-cli releases files $VERSION-$JSVERSION upload-sourcemaps --strip-prefix . --rewrite main.jsbundle main.jsbundle.map --dist $VERSIONCODE
bundle exec fastlane upload_debug_symbols_sentry_ios Contents of fastlane:
|
Thanks @jayshah123 for the detailled response, we'll investigate and follow up here. |
Thanks @kahest . |
@jayshah123 a link would be appreciated. We can keep it in this current issue until we know if it's a separate one |
Link to the second issue here |
Let us know if something can be done here, we are trying to investigate this issue and missing symbolication makes it harder. |
Hi, I see that you are missing the Sentry config in your Metro configuration. The missing Sentry Config will cause that the generated Debug IDs are not used due to missing Debug ID polyfill. The links you shared are containing native iOS crashes. To symbolicate those you need to make sure native Debug Files are uploaded. You can do that automatically during the Xcode build by using https://docs.sentry.io/platforms/react-native/manual-setup/manual-setup/#configure-automatic-debug-symbols-upload |
Checking the same, and will report if face any issues. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: @sentry/react-native@5.20.0
react-native
version: 0.73.9Are 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:
Link to issue
Configuration:
(
@sentry/react-native
)In our
metro.config.js
, we use@expo/metro-config
as a starting point like below:Upload steps for iOS (after codepush release-react):
Upload steps for Android (after codepush release-react):
I have the following issue:
[Description]
index.android.bundle.map
json file.# debugId
comment in minified code bundle seems to be coming from:node_modules/@expo/metro-config/build/serializer/fork/baseJSBundle.js
Steps to reproduce:
captureException
Actual result:
Unsymbolicated stack trace
Expected result:
Symbolicated stack trace.
The text was updated successfully, but these errors were encountered: