diff --git a/src/platform-includes/debug-symbols-apple/_default.mdx b/src/platform-includes/debug-symbols-apple/_default.mdx index 39afad837d8a9..686dfc620196b 100644 --- a/src/platform-includes/debug-symbols-apple/_default.mdx +++ b/src/platform-includes/debug-symbols-apple/_default.mdx @@ -174,6 +174,7 @@ When using Fastlane's _upload_to_testflight_ action, it's recommended to pass th As of April 25th, 2023, the [App Store](https://developer.apple.com/news/?id=jd9wcyov) no longer accepts submissions with bitcode enabled. +The instructions below will only work retroactively for apps that were submitted before this date and that included bitcode. diff --git a/src/platform-includes/getting-started-install/javascript.cordova.mdx b/src/platform-includes/getting-started-install/javascript.cordova.mdx index 9b163ab633781..28f0979306060 100644 --- a/src/platform-includes/getting-started-install/javascript.cordova.mdx +++ b/src/platform-includes/getting-started-install/javascript.cordova.mdx @@ -8,4 +8,4 @@ The [Sentry Wizard](https://github.com/getsentry/sentry-wizard) will patch your ### iOS Specifics -When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. However, if you are using bitcode, you will need to disable the “Upload Debug Symbols to Sentry” build phase and then separately upload debug symbols from iTunes Connect to Sentry. +When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. diff --git a/src/platform-includes/getting-started-install/react-native.mdx b/src/platform-includes/getting-started-install/react-native.mdx index c1201e58b5d8d..b3e61d66df87b 100644 --- a/src/platform-includes/getting-started-install/react-native.mdx +++ b/src/platform-includes/getting-started-install/react-native.mdx @@ -39,7 +39,7 @@ Make sure that the version of `@sentry/react-native` matches what `sentry-expo` ### iOS Specifics -When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. However, if you are using bitcode, you will need to disable the “Upload Debug Symbols to Sentry” build phase and then separately upload debug symbols from iTunes Connect to Sentry. +When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. ### Android Specifics diff --git a/src/platforms/unity/native-support/index.mdx b/src/platforms/unity/native-support/index.mdx index 590e944530287..5b003dee20c9c 100644 --- a/src/platforms/unity/native-support/index.mdx +++ b/src/platforms/unity/native-support/index.mdx @@ -50,18 +50,16 @@ Sentry requires [debug information files](/platforms/unity/data-management/debug The automated debug symbols upload is enabled by default but requires configuration. Go to **Tools > Sentry > Editor** to enter the [Auth Token](https://sentry.io/api/), Organization Slug, and the Project Name. Note that the Unity SDK creates a file at `Assets/Plugins/Sentry/SentryCliOptions.asset` to store the configuration, that should **not** be made publicly available. -### iOS - dSYM and Bitcode +### iOS - dSYM -Debug information files on the iOS platform are called dSYM, and the way to obtain them differs depending on whether `Enable Bitcode` is set to `true` in your Xcode project. +Debug information files on the iOS platform are called dSYM. -For Sentry to symbolicate your crash logs and with `bitcode` enabled, we need two types of files: +For Sentry to symbolicate your crash logs we need two types of files: -1. `dSYM` files available only **after** App Store Connect finishes processing the build +1. `dSYM` that the automated symbols upload will pick up at the end of the build process without further action required. 2. `BCSymbolMap` files that are created during the archiving process -The automated symbol upload will take care of the `BCSymbolMap` files by processing them during the archiving process. To provide the dSYM files to Sentry, you can either set up the [Sentry App Store Connect Integration](/platforms/apple/guides/ios/dsym/#appstore-connect) so Sentry can fetch them for you, or download them from Apple and then upload them [manually using sentry-cli](/platforms/apple/guides/ios/dsym/#sentry-cli). - -With `bitcode` disabled, the automated symbols upload will pick up the `dSYM` files at the end of the build process without further action required. +The automated symbol upload will take care of the `BCSymbolMap` files by processing them during the archiving process. ### Manual Upload Using sentry-cli diff --git a/src/wizard/react-native/index.md b/src/wizard/react-native/index.md index bdfeb00de3189..8773c6516f0d4 100644 --- a/src/wizard/react-native/index.md +++ b/src/wizard/react-native/index.md @@ -17,7 +17,7 @@ npx @sentry/wizard -s -i reactNative [Sentry Wizard](https://github.com/getsentry/sentry-wizard) will patch your project accordingly, though you can [setup manually](/platforms/react-native/manual-setup/manual-setup/) if you prefer. -- iOS Specifics: When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. However, if you are using bitcode, you will need to disable the “Upload Debug Symbols to Sentry” build phase and then separately upload debug symbols from iTunes Connect to Sentry. +- iOS Specifics: When you use Xcode, you can hook directly into the build process to upload debug symbols and source maps. ``` - Android Specifics: We hook into Gradle for the source map build process. When you run `./gradlew assembleRelease`, source maps are automatically built and uploaded to Sentry. If you have enabled Gradle's `org.gradle.configureondemand` feature, you'll need a clean build, or you'll need to disable this feature to upload the source map on every build by setting `org.gradle.configureondemand=false` or remove it. ### Initialize the SDK