Using expo-datadog and @sentry/react-native/expo in Expo results in missing bundle file
#3941
Comments
github-project-automation
bot
moved this to Needs Discussion
in Mobile & Cross Platform SDK
|
Hey @lepskiy thanks for reporting, we'll take a look. Note that due to conference and PTOs we might be a bit slower to respond than usual. Also, can you confirm that this is the same issue as you reported in #3551 (comment)? |
|
Please also refer to our migration guide from |
Confirm, this is a duplicate. I've just decided to create a new ticket instead of the comment in the closed one. |
|
Hi @lepskiy, The message The log you shared is from a Debug build. Sentry doesn't look for a source maps in debug builds as no bundles are generated. The Sentry log from above: |
krystofwoldrich
moved this from Needs Discussion
to Needs More Information
in Mobile & Cross Platform SDK
|
Had the same EAS build error with both Alternatively, when either one of the config plugins is excluded, the app builds and runs successfully. Tested with Crash report indicates an uncaught exception throwing RCTFatal in |
getsantry
bot
added
Waiting for: Product Owner
and removed
Waiting for: Community
labels
getsantry
bot
moved this from Waiting for: Community
to Waiting for: Product Owner
in GitHub Issues with 👀 3
Completely the same. After moving DataDog below Sentry the build is fixed but the build is crashed on iOS (on Android works fine). |
|
Hi @lepskiy and @jhbarnett, The conclusion is using |
|
Would you be able to provide a reproducible example? |
|
Small note, I see that the shared Could you regenerate the native projects or update the build phase manually to use |
krystofwoldrich
changed the title
expo-datadog and @sentry/react-native/expo in Expo results in missing bundle file
krystofwoldrich
moved this from Needs More Information
to Needs Investigation
in Mobile & Cross Platform SDK
|
How to use
Both When both plugins are used the build phase results in valid bash script, but the executed commands will fail to produce the JS Bundle. ✅ Recommendation 1: Use only one of the plugins. If you are using only of the SDKs to capture errors, use its plugin. The other SDK if not used for errors doesn't need the auto debug files upload. ✅ Recommendation 2: Use none of the plugins and upload the debug files manually. To see how to generate and upload source maps you can follow this guide https://docs.sentry.io/platforms/react-native/sourcemaps/uploading/expo-advanced/#manual-upload-for-hermes-release
|
|
Remarks: Execution order export SOURCEMAP_FILE=$DERIVED_FILE_DIR/main.jsbundle.map
if [[ -z "$DATADOG_CI_EXEC" ]]; then
DATADOG_CI_EXEC="$("$NODE_BINARY" --print "require('path').resolve(require('path').dirname(require.resolve('@datadog/datadog-ci/package.json')), '../../.bin/datadog-ci')")";
# Check if the file exists and is executable
if [[ -x "$DATADOG_CI_EXEC" ]]; then
export DATADOG_CI_EXEC;
else
echo "Error: DATADOG_CI_EXEC does not exist or is not executable";
exit 1;
fi
fi
/bin/sh `"$NODE_BINARY" --print "require('path').dirname(require.resolve('@sentry/react-native/package.json')) + '/scripts/sentry-xcode.sh'"` $DATADOG_CI_EXEC react-native xcode `"$NODE_BINARY" --print "require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'"`The issue is Execution order /bin/sh `"$NODE_BINARY" --print "require('path').dirname(require.resolve('@sentry/react-native/package.json')) + '/scripts/sentry-xcode.sh'"` `"$NODE_BINARY" --print "require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'"`
if [[ -z "$DATADOG_CI_EXEC" ]]; then
DATADOG_CI_EXEC="$("$NODE_BINARY" --print "require('path').resolve(require('path').dirname(require.resolve('@datadog/datadog-ci/package.json')), '../../.bin/datadog-ci')")";
# Check if the file exists and is executable
if [[ -x "$DATADOG_CI_EXEC" ]]; then
export DATADOG_CI_EXEC;
else
echo "Error: DATADOG_CI_EXEC does not exist or is not executable";
exit 1;
fi
fi
$DATADOG_CI_EXEC react-native xcode `"$NODE_BINARY" --print "require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'"`In this case |
krystofwoldrich
moved this from Needs Investigation
to Needs Discussion
in Mobile & Cross Platform SDK
krystofwoldrich
moved this from Needs Discussion
to Backlog
in Mobile & Cross Platform SDK
OS:
Platform:
SDK:
@sentry/react-native(>= 1.0.0)react-native-sentry(<= 0.43.2)SDK version: 5.20.0
react-nativeversion: 0.73.6Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
(
@sentry/react-native)I have the following issue:
After upgrading to Expo 50 and migrating from sentry-expo to @sentry/react-native the build (using remote EAS Build) started failing.
Steps to reproduce:
Actual result:
EAS build is failed with the error:
XCode logs:
Expected result:
Build finish succesfully.
The text was updated successfully, but these errors were encountered: