Closed allan-simon closed 3 years ago
are you using EAS or expo-cli
for your builds?
eas (and thanks for taking a look in my issue :) )
sure thing! Can you let me know if a classic build (expo build:ios
) works for you?
I have a feeling this is due to the fact that EAS builds function a little differently than classic builds. You may want to try installing @sentry/react-native
then rebuilding
no problem, i've launched the command, i'm now waiting for the build
the build has finished (is it normal that it was MUCH faster than on EAS ? on eas it tooks reliably 20 minutes everytimes ) , however I can't figured out how to install the ipa, as the build result page has just a "download artifacts" buttons at the opposite of EAS build page.
right now it's simply donwloading the ipa file as a simple file
thanks for the link , ah so impossible without a mac laptop ? :(
https://blog.bam.tech/developer-news/installing-an-ipa-on-your-ios-device-from-command-line-in-osx-or-linux i will test that , seems not all hope is lost :)
I had this same issue with EAS, I have a hunch that it's using the bare workflow under the hood rather than managed. I solved it by following the steps for the bare workflow here:
https://docs.expo.io/guides/using-sentry/#additional-bare-workflow-setup
that's exactly right @ajgrover, although this means you won't have a sentry.properties
file available
@cruzach running the yarn sentry-wizard ...
command in that link generates {ios,android}/sentry.properties
files actually!
on a somewhat related note, EAS build is also incompatible with some other libraries (notably expo-constants
) which isn't super clear from the docs and leads to a similar hard-to-debug crash. i can open an issue on the main repo if that would be helpful.
running the yarn sentry-wizard ... command in that link generates {ios,android}/sentry.properties files actually!
ah, so you're ejecting before triggering the EAS Build?
i can open an issue on the main repo if that would be helpful.
yep that'd be great
that would be awesome, because even by removing sentry-expo, i also got some crash latter, and i'm actually using expo-constants ^^ @cruzach it's getting late there, so I will be able to test the installation in 12 hours something like that, thanks again for your help
@cruzach nope, still using the managed workflow, maybe the generated config files aren't actually doing anything. I haven't tested any crashes yet.
My guess is the sourcemaps won't actually be uploaded in that case, until you expo publish
Since managed workflow isn't fully supported on EAS yet, I'm going to close this issue. It may build successfully if you install react native sentry, but the sourcemap upload hook won't be triggered during EAS Builds so you won't get sourcemaps until you expo publish
after building.
However- EAS Build for bare workflow is fully supported for sentry-expo
I'll make note to keep this in mind as EAS Build support for managed workflow comes along 😄
@allan-simon Did you figure out a solution? I'm running into the same error with the exact same crash report.
no at the end we're using bitrise not eas for our CD pipeline
Summary
I use sentry as described in the doc, it works fine when using expo-go , but crash when building it for my phone using EAS (i have no mac, so no way to tell what would happen with Xcode)
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)
0.40.0
Environment
Reproducible demo or steps to reproduce from a blank project
Here the crash report