sentry-cli: error: http error: generic error (504) on dSYM upload

Hi,

I have just integrated setnry-cli into our build pipeline for our iOS app and I’m getting the following error message when attempting to upload symbol files. The error happens about 80% of the time I attempt to run sentry-cli.

I am using the fastlane sentry gem and providing it with the correct auth_token, org_slug & project_slug. I have also tried integrating sentry-cli directly into a run script build phase in xcode with the same result.

[13:50:22]: --------------------------------
[13:50:22]: --- Step: sentry_upload_dsym ---
[13:50:22]: --------------------------------
[13:50:23]: sentry-cli 1.29.0 installed!
[13:50:23]: Starting sentry-cli...
[13:51:45]: Batch 1
[13:51:45]: > Found 18 debug symbol files.
[13:51:45]: > Checking for missing debug symbol files on server
[13:51:45]: > Compressing 2 missing debug symbol files
[13:51:45]: > Uploading debug symbol files
[13:51:45]: error: http error: generic error (504)

I have seen https://github.com/getsentry/sentry-cli/issues/89 and seen that it was closed as a duplicate of https://github.com/getsentry/sentry-cli/issues/86 however I would disagree that this issue 86 and 89 are the same as they manifest in two different ways (HTTP 504 vs HTTP 413).

I’d love some help with this as this is currently blocking me from adopting Sentry and dropping Fabric for my company’s iOS and Android apps.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 18 (7 by maintainers)

Most upvoted comments

Reopening this issue as we’re now getting this response:

[14:53:09]: [INFO] sentry_cli::api body: {"detail": "Internal Error", "errorId": "1ca8d9b045854dc59abe2f512f6d1a88"}
[14:53:09]: error: http error: Internal Error (500)

I was using the build Armin sent me which I think was from 82905b708472a856e5ca90da970d8d9f7e78b9bd

I have in an attempt to address this rebuilt sentry-cli from current master HEAD d71a919 and still get this 500 error 100% of the time I attempt to use sentry-cli. I’ll revert back to the 1.29.1 release tag as the intermittent failure is better than the constant failure but figured you’d appreciate the heads up.

joejcon1 on Feb 16, 2018