-
-
Notifications
You must be signed in to change notification settings - Fork 343
Uploaded Android bundle is 0MB and event processing keeps failing due to it #2683
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
Comments
@StampixSMO RN 0.70.6 has Hermes enabled by default, not sure if you had before. |
Hi @marandaneto Thanks for the reply, appreciated! We've had Hermes quite a while already, so don't think that's the issue here. Additionally, we've got the latest SDK version (see above) in the issue description. For the
Any further suggestions we can try? Edit: also adding the output of our build:
|
@StampixSMO being 0 bytes is fine I don't remember if for Hermes or RAM bundles, have to check it. |
Hi @StampixSMO, |
Publicly I cannot easily share an example app without reproducing our entire app including fastlane CI etc .. Is there an option to privately share this? Using bare workflow btw |
@StampixSMO Would you be able to recreate the issue with a clean project, just setting up the minimum needed, maybe the issue show even without Fastlane? |
A
Steps to reproduce... |
Allow me some time to set this up and try to reproduce, be back soon. |
Hey @krystofwoldrich I've set up a new project and new project, build the app in release mode and the bundle is again 0MB. So to me, it's weird that the main bundle is 0MB, because I thought that was the reason we keep getting "Invalid location in sourcemap" on ALL our Android events in our main app. We've tried the CLI debugging a few times already, but the only clue I could find is the empty bundle file. The output of the CLI is always the same:
Indeed, the issue event mentions |
@StampixSMO Sadly I don't know what to do at this moment. The only suggestion I have is to compare the newly created project to the original one and try to find the differences in settings, RN version, etc. |
@krystofwoldrich Is it normal that the bundle is 0MB? |
Yes, as mentioned here #2683 (comment) About the issue, @StampixSMO please take a look into @krystofwoldrich questions #2683 (comment) |
@StampixSMO Any updates? |
@krystofwoldrich No, I've been out and haven't been able to look into the diff. On my TODOs! |
I will close this for now. But please comment down below when you get back to it and we can reopen it and investigate more. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 4.10.1
react-native
version: 0.70.6Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
https://sentry.io/organizations/stampix-zb/issues/3496972388/?project=6259211&query=is%3Aunresolved+os.name%3AAndroid&referrer=issue-stream&statsPeriod=14d
Configuration:
(
@sentry/react-native
)Note that we've just now disabled auto initialization, the issue at hand was present before we did disabled this.
I have following issue:
Every new release suddenly started having empty Android bundles, giving us the

Invalid location in sourcemap
errors at the top of Android-reported events.Using the Sentry CLI to debug the particular events reveals the same and the sourcemap uploads in the project Settings also clearly shows it's empty (see screenshot).
Note that this used to work in the past, but it's hard to debug where it started occurring since the older events are long removed due to retention periods.
For iOS, this works perfectly and all is well.
Steps to reproduce:
Just make a release bundle, which automatically uploads the bundle to our Sentry environment.
Actual result:
Minified stack traces in our events and an error banner on top.
Expected result:
Proper reported events with stack traces
The text was updated successfully, but these errors were encountered: