-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Android sourcemapOutput detection broken? #772
Comments
cc @HazAT |
Sorry about that, we'll take a look. |
Thanks. I'll give it a go, but not before monday though. I am not quite sure, but I think my --bundle-output is set but not the --sourcemap-output. But as I said this only by looking at code, I would need to run this to see how it behaves. |
@muxe sure :) but I'd say that in your case |
Fixed by #777 |
Still facing this issue in 1.3.7 |
@amogh-jrules mind filling a bug with all the versioning + logs? thanks :) |
OS:
Platform:
SDK:
@sentry/react-native
react-native-sentry
SDK version: 1.3.0
react-native
version: 0.59.10Init Code:
I have following issue:
My bundle is not producing any sourcemaps and then the upload of the sourcemap fails.
I think there is an issue with forcing sourcemap output:
My default bundle command does NOT have a --sourcemap-output in.
It starts here https://github.com/getsentry/sentry-react-native/blob/master/sentry.gradle#L45
Then here https://github.com/getsentry/sentry-react-native/blob/master/sentry.gradle#L212 it tries to get the sourcemapOutput path.
So these lines wont find a sourcemapOutput https://github.com/getsentry/sentry-react-native/blob/master/sentry.gradle#L180-L186 BUT then here
https://github.com/getsentry/sentry-react-native/blob/master/sentry.gradle#L195-L198 some weird sourcemapOutput is returned.
So the script thinks there was a --sourcemap-output defined and does not force the arg, hence no sourcemap will be generated but it still expects a sourcemap to be there.
Or am I missing something?
Steps to reproduce:
Actual result:
Expected result:
The text was updated successfully, but these errors were encountered: