-
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
Sourcemaps of self-hosted bundles not resolved #145
Comments
I have the same issue with self-hosted, the only difference is that I'm using Bare workflow (no Managed). |
Try the workaround I shared in my original issue description, it should work as is in bare workflow too. |
I need to import
|
I fixed
I applied your workaround but doesn't work for me, sentry can't found the sourcemaps. I also tested change the filename but doesn't work. I'm testing on iOS
|
This also happen on non self-hosted updated #149 |
hm yeah seems like we should use the same what we're trying to match here is the bundle filename, which should be the same whether you @peter-jozsa is this on iOS, android, or both? |
@RodolfoGS i believe this is unrelated to your issue in the bare workflow |
added docs for this here- expo/expo@ded7182 |
sorry for not replying, I tested this only on iOS but I think it is also related to since the built-in RewriteFrames checks the CDN URL of expo which will never work for us who self-hosts their bundles. |
@peter-jozsa are you saying you can't overwrite the default RewriteFrames integration? You should be able to do that |
No, everything is okay, our app works fine with the workaround I suggested in my original issue description. I just tried to reply to your earlier message 👍 Thanks for adding it to your docs!
|
Hey there,
We are trying to use Sentry in our self-hosted managed Expo app but unfortunately sourcemaps are not resolved when an issue is reported. We upload sourcemaps of the bundle in
postExport
hook like it is suggested in the docs, but Sentry does not use them.The main reason for this is because hardcoded Expo CDN url is used to determine how frame filenames should be normalized. Since our app does not use the Expo CDN url the original frame filename is sent along the issue and Sentry won't find the uploaded sourcemaps.
We could easily workaround the issue by adding the
RewriteFrames
integration explicitly to theSentry.init
call, like:I think docs should mention how people should use this package when they don't use the Expo CDN to deploy their apps.
Hope I could help someone :)
The text was updated successfully, but these errors were encountered: