Skip to main content

Why is there an extra slash in the debug ID path when accessing custom repositories for debug symbols?

Issue

I want to know why custom debug-symbol repository paths split the debug ID with a slash (for example debug ID bb752254 → path bb/752254).

Applies To

  • All SaaS Customers

  • Business and Enterprise plans

  • Custom symbol repositories / Debug Files

Resolution

Yes, that interpretation is correct. In Sentry’s Unified debug-file layout, the path is split after the first two lowercase hex characters of the build_id:

<first 2 hex chars>/<remaining build_id>/debuginfo

So for b5381a457906d279073822a5ceb24c4bfef94ddb, the path becomes:

b5/381a457906d279073822a5ceb24c4bfef94ddb/debuginfo

In Project Settings → Debug Files → Custom Repositories, set Directory Layout to Unified Symbol Server Layout if you want this structure. Details: Unified layout.

Did this answer your question?