Closed mfkrause closed 2 years ago
This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed.
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.
Summary
We've implemented Sentry in our Expo EAS app using this package and
@sentry/react-native
. Everything worked fine up to the uploading of the source maps. However, a few days into it, we've noticed a ton of thrown issues on Sentry in regards to our audio module powered byreact-native-sound
. Turns out, that in our iOS production builds the app wasn't able to find its audio assets at all. All attempts to load an audio file failed with the native iOS error "OSStatus error 2003334207", meaning that the asset couldn't be found. In the development builds and on Android everything works fine. As soon as we remove Sentry from the app, it works fine again.I suspect this has something to do with the asset bundling of
expo-updates
but am not sure, since I haven't found a way how to use this package withoutexpo-updates
and the docs aren't too clear about why this package is needed in the first place. If I could isolate this to Expo Updates, I'd move the issue to the main repo. There has been an issue in the main Expo repo about a year ago about exactly this problem in regards toexpo-updates
- from the comments, this should have been fixed though. I've checkedyarn why expo-asset
and the version is 8.4.6, while the bug was supposed to be fixed in 8.3.3. So again not sure if this really comes from Expo Updates.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
Reproducible demo or steps to reproduce from a blank project
Can't share a simple code snippet for repro - however I'd be happy to provide a quick demo project if needed. Setting up a repro isn't too complicated, though: