No such file exception when uploading source maps
tomrom-pomelo opened this issue · comments
Summary
When running EAS builds, we seeing the following:
> Task :app:createBundleReleaseJsAndAssets_SentryUpload_com.pomelocare.patient.dev@1.0.30+30_30 FAILED
Processing react-native sourcemaps for Sentry upload.
> Task :app:createBundleReleaseJsAndAssets_SentryUploadCleanUp SKIPPED
[stderr]
INFO 2023-09-08 15:38:10.690003885 +00:00 Loaded file referenced by SENTRY_PROPERTIES (/home/expo/workingdir/build/clients/apps/mobile/android/sentry.properties)
We set up sentry-expo
plugin exactly as described in https://docs.expo.dev/guides/using-sentry/ . We are using n
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
Android
SDK Version (managed workflow only)
49
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.5.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.17.0 - ~/.volta/tools/image/node/16.17.0/bin/node
npm: 8.15.0 - ~/.volta/tools/image/npm/8.15.0/bin/npm
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
API Levels: 29, 31, 32, 33
Build Tools: 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0, 33.0.0, 34.0.0
System Images: android-29 | ARM 64 v8a, android-32 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
npmPackages:
@expo/metro-config: 0.5.2 => 0.5.2
babel-preset-expo: 9.3.0 => 9.3.0
expo: 49.0.7 => 49.0.7
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.72.3 => 0.72.3
react-native-web: ~0.18.10 => 0.18.12
npmGlobalPackages:
eas-cli: 2.2.0
expo-cli: 6.0.6
Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
We are using
"@sentry/cli": "2.20.7",
"@sentry/react-native": "5.9.1",
"sentry-expo": "7.0.1",
Running eas build for android creates this issue.
Fixed by upgrading to expo 49.0.9 and expo-cli 0.10.11