Task :app:bundleReleaseJsAndAssets_SentryUpload FAILED #578
Labels
Comments
|
Can you try to cd android/ and then ./gradlew assembleRelease --debug ? For me this error was due to a 413 status code made by our self hosted sentry. The source maps being uploaded were bigger than our server size limitation. By increasing the So check first if this is not related to sourcemaps / server. That would be nice to have a repro or something as your message is not helping that much. Hope it will help you. |
|
This happened to me after changing the project name in the Sentry dashboard. If you do this, you'd also have to change the name in the following files: |
|
@costerik make sure the org and project are match exactly the ones shown in the browser url when you navigate to your project. |
|
I'm having the same issue and have tried the proposed methods above to no avail.
Will try to provide a repro case shortly. |
|
Any update? I have the same issue when I try to make a build |
|
+1 |
|
Can someone try to run the build command with the --debug flag and then copy-paste the logs here ? ( Thanks to this I was able to know that my problem was source-maps size related when the build process hit the :react-native-sentry dep |
|
|
@maieonbrix This error log contains the same error message that the issue is referring to: |
|
This issue could be related to react-native-0.60.+ I am on RN 0.60.3 and react-native-sentry 0.43.2 |
|
So I made a build successfully. Immediate next one fails. Now can't build. Any updates on this? |
|
In my case, the problem occured when I wanted to make staging builds. I used to just run a project.ext.react = [
entryFile: "index.js",
bundleInStaging: true, // Add this
bundleInInternalTest: true, // Add this
bundleInRelease: true
]
|
|
this is still an issue EDIT: I copied the new token and reverted to the old package using the new token in (ios/sentry.properties and android/sentry.properties) - |
|
haven't been able to build an android release in several weeks (since updating to @sentry/react-native) node: v12.10.0 seems that |
|
I recreated There is no folder UPDATE: Sorry, it was my fault. I added |
7 tasks
|
Any news here? I am experiencing it as well. |
|
Its been 6 months please anything? 🙏 |
|
I've been having this issue too. My issue when running with When I build iOS, I save the build artifacts (IPA, xcarchive, etc) under Just removing my Hope this helps somebody. |
|
For me error occurred because I had cli.executable=node_modules/@sentry/react-native/node_modules/@sentry/cli/bin/sentry-cli (incorrect path) instead of cli.executable=node_modules/@sentry/cli/bin/sentry-cli in android/sentry.propetries. |
|
One thing made it to work on Android - THE code: |
|
Hi, I'm working on android app and I had the same build error and it appears to be caused by |
|
It happened to me when sentry.io server was down. When it was up, the build succeeded. Also, the error can happen if your JS bundle fails to build and thus the sentry task fails right after. |
|
Thanks its work |
|
I just had the same issue. I assumed it was because I changed the organisation slug on sentry, but I updated the environment variables. But it seems you also have to create a new auth token, after you change org. slug. The old one didn't work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0Config:
I have following issue:
Actual result:
The text was updated successfully, but these errors were encountered: