You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long-story short, sentry-expo requires version 7.7 of Sentry JS. We want to bump to ~7.28. (see here) Because of this constraint, the @sentry/react-native library (needed for native reporting) is constrained to be at version3.2 or lower. (iOS production builds will fail due to Podfile dep issues). @sentry/react-native is currently at 4.6.1 and version 5.0.0-alpha.6 is already out.
I believe there are some issues with the version of @sentry/react-native. In Android 6, 7 and 8, for example, any app containing it will simply not open. This is due to an error in this version of Sentry. I see multiple crash reports in Android Vitals about this. Android 7 is 5% of global users.
I would assume (or blindly hope) that these issues are resolved in later versions of @sentry/react-native, therefore it might be worth bumping the version in this repo to allow for that to be installed.
Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!
Summary
Long-story short,
sentry-expo
requires version 7.7 of Sentry JS. We want to bump to ~7.28. (see here) Because of this constraint, the@sentry/react-native
library (needed for native reporting) is constrained to be at version3.2
or lower. (iOS production builds will fail due to Podfile dep issues).@sentry/react-native
is currently at4.6.1
and version5.0.0-alpha.6
is already out.I believe there are some issues with the version of
@sentry/react-native
. In Android 6, 7 and 8, for example, any app containing it will simply not open. This is due to an error in this version of Sentry. I see multiple crash reports in Android Vitals about this. Android 7 is 5% of global users.I would assume (or blindly hope) that these issues are resolved in later versions of
@sentry/react-native
, therefore it might be worth bumping the version in this repo to allow for that to be installed.Managed or bare workflow? If you have
ios/
orandroid/
directories in your project, the answer is bare!managed
What platform(s) does this occur on?
iOS
SDK Version (managed workflow only)
44
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 12.4
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
Yarn: 1.22.18 - /opt/homebrew/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
Watchman: 2022.10.03.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 30, 31
Build Tools: 29.0.2, 30.0.2, 31.0.0, 33.0.0
System Images: android-24 | Google APIs ARM 64 v8a, android-31 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
npmPackages:
@expo/metro-config: ^0.3.9 => 0.3.21
expo: ^45.0.0 => 45.0.8
react: 17.0.2 => 17.0.2
react-dom: 17.0.2 => 17.0.2
react-native: 0.68.2 => 0.68.2
react-native-web: 0.17.7 => 0.17.7
npmGlobalPackages:
eas-cli: 0.55.1
expo-cli: 6.0.5
Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
package.json
The text was updated successfully, but these errors were encountered: