-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a guide on how to generate/upload sourcemaps when running eas build? #376
Comments
Would second it, we recently switched from I assume this is more on It's tracked in here I suppose |
Sourcemaps aren't even uploading for me when running
My app.json is setup correctly:
and I've configured SENTRY_AUTH_TOKEN in Eas Secrets. I can't see what I'm missing. |
Hello everyone, Guide on how to set up source maps: https://docs.sentry.io/platforms/react-native/sourcemaps/uploading/expo/ Update to https://github.com/getsentry/sentry-react-native/releases/tag/5.16.0 or newer to get all the new features. Migration guides available: |
thanks @krystofwoldrich for the sentry team that made this possible! |
As i mentioned in the title, i am curious if there is a well-documented and battle-tested guide on this, because i think people can get confused. The expo documentation although is very detailed, i didn't find a good solution for
eas build
.Currently what works for me is creating a new build with
eas build
then runningeas update
to generate the dist folder for the bundles. But then it gets kinda messy, especially for the developer who is accustomed to the expo ecosystem, you have to rename the bundle files (especially if you are using hermes), then run a long sentry-cli command to upload the sourcemaps to that given release and even then sometimes it will not work.I don't think this is very intuitive, so i am curious if there is or will be some updates on this in the future, maybe better documentation or a simplified process to generate the sourcemaps and assign it to your build.
I want to mention that i am grateful for the expo team, it made the development in react native tremendously easier, i just wanted to get some information on this.
The text was updated successfully, but these errors were encountered: