Symbolication fails for new reports after several weeks of successful reports #107247
Description
Introduction
We are seeing a problem where symbolication of our most recent logs fail, after a period of time where they initially symbolicate correctly.
We have already reported this bug through the support channels. The Sentry support team recommended that we escalate the issue by submitting an issue through the Github repository.
To be clear, we don't use the Native SDK, and instead upload custom written logs manually using Sentry's API.
Problem Statement
We upload Debug Files from our CI pipeline after building the product (an audio plugin which runs within a host program that we did not write).
We are not using the Native SDK, due to a conflict with third party license and protection software. When the product crashes, we upload a crash log to Sentry using the Sentry API. We can then view the log through the Sentry web interface.
For many months we've been successfully uploading crash logs. When viewed in the Sentry web interface we can see the function names and modules correctly (the files have been properly symbolicated).
However, in the last few weeks, new crashes for that project seem to no longer symbolicate correctly.
Recently, a 2nd product, which had been symbolicating properly for many weeks in Sentry, is no longer symbolicating. So the problem does not appear to be related to a single product, nor any changes that we have made to the release or to the uploaded debug files, or to our upload functions.
Things That We Have Checked
At first we thought the Debug Files may have been deleted somehow from the Sentry system, but after checking we can see that the files are still available.
Our macOS build upload commands look like this:
sentry-cli upload-dsym --include-sources --org ${SENTRY_ORG} --project ${SENTRY_PROJECT} \
"./${PRODUCT_NAME}_artefacts/symbols/${BINARY_NAME_UPDATE}.vst3.dSYM" \
"./${PRODUCT_NAME}_artefacts/symbols/${BINARY_NAME_UPDATE}.aaxplugin.dSYM" \
"./${PRODUCT_NAME}_artefacts/symbols/${BINARY_NAME_UPDATE}.component.dSYM"
Our PC build upload commands look like this:
sentry-cli debug-files upload \
--org ${SENTRY_ORG} \
--project ${SENTRY_PROJECT} \
--wait \
--include-sources \
"./${PRODUCT_NAME}_artefacts/Protect/AAX/${BINARY_NAME_UPDATE}.pdb" \
"./${PRODUCT_NAME}_artefacts/Protect/VST3/${BINARY_NAME_UPDATE}.pdb"
The only upload warning that we are seeing in the pipeline is this one:
WARN 2026-01-21 17:46:29.424296 +00:00 Source exceeded maximum item size limit (2564629). /Applications/Xcode-15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/include/arm_neon.h
The image UUIDs / debug IDs in the crash logs exactly match those in the uploaded dSYM/PDB files.
The code type, architecture, and binary name are aligned.
The crash event contains a valid debug_meta / image list.
The copy protection scheme is not modifying the build after the debug ID has been recorded.