‘internal server error’ when uploading debug files

[hak-ioki]

CLI Version

2.31.2

Operating System and Architecture

• macOS (arm64)
• macOS (x86_64)
• Linux (i686)
• Linux (x86_64)
• Linux (armv7)
• Linux (aarch64)
• Windows (i686)
• Windows (x86_64)

Operating System Version

macOS 14.4.1

Link to reproduction repository

No response

CLI Command

sentry-cli upload-dif "$DWARF_DSYM_FOLDER_PATH" 2>&1 >/dev/null --log-level=debug

Exact Reproduction Steps

When I build the Xcode project, it can't upload the symbols. Here is the summary of the logs:

> Found 123 debug information files
> Prepared debug information files for upload
> File processing complete:

    ERROR Common
        internal server error
    ERROR CommonAirship
        internal server error
    ERROR DBFFM
        internal server error

Error: some symbols did not process correctly
error: sentry-cli exit with 1

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

Expected Results

Should upload debug files successfully. I saw two[1, 2] different issues that are related to our issue, and I uploaded sentry-cli after I saw this fix, but it didn't work again.

Actual Results

It couldn't upload debug files.

Logs

detailed-logs.zip

[szokeasaurusrex]

Can you please verify in Sentry whether your debug files indeed are missing? I don't think these internal server error logs are originating from the Sentry CLI, so perhaps there is some other problem?

[hak-ioki]

Hey @szokeasaurusrex , thank you for the quick response, these files are part of our project. How can I verify them? They are our frameworks.

[szokeasaurusrex]

@hak-ioki You should be able to see your debug files somewhere in your Sentry project (or maybe org) settings. Can you check whether these files show up there?

You can also check your errors in Sentry. If all of your errors are showing proper stack traces, that indicates most likely that we have you debug files. If errors are missing stack traces, then we are missing debug files or there is some other problem with your setup

[hak-ioki]

@szokeasaurusrex is this what you meant:

If yes, then why does the website still show this error:

[szokeasaurusrex]

Yes, that is what I meant @hak-ioki.

I have never seen this error before and I have no idea what might be causing it. Since the debug file is being uploaded apparently, though, I'm guessing this is possibly a problem in Sentry itself, not in the CLI. I am going to transfer your issue to the Sentry repository so that someone more familiar with that part of the product can assist.

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[szokeasaurusrex]

More details are provided on getsentry/sentry-cli#2068, which was closed in favor of this issue

[hak-ioki]

@szokeasaurusrex, my last try was successful and I'm not sure why, maybe it was a temporary issue, but for the last 10 minutes, it worked :) I appreciate your help. The last error disappeared on the website, sorry for the confusion. So, I'm closing the issue.