Deobfuscate Stack Traces
When your application is protected with Shield, crash reports and stack traces will contain obfuscated names. ByteHide automatically handles deobfuscation so you can debug production issues with the original class and method names.
How It Works
Every time you build your application with Shield, a mapping file is generated and automatically uploaded to the ByteHide Cloud Panel. This mapping file contains the relationship between the original names and the obfuscated names.
When you encounter an obfuscated stack trace from a crash report, you can decode it instantly from the Cloud Panel or via the API. No additional setup is required: if your project has a valid token, mappings are uploaded and available automatically.
Requirements
To decode stack traces, you will need:
- Your Project Token
- Your Protection Secret (auto-generated during protection, visible in the Cloud Panel build history)
Decoding via the Cloud Panel
The simplest way to decode a stack trace:
- Go to your project in the ByteHide Cloud Panel
- In the history section, click the three dots (actions) for the build you want to decode
- Select Deobfuscate trace
- Paste your obfuscated stack trace and click Deobfuscate Trace
Click to expand
The panel returns the original, readable stack trace with the real class and method names:
Click to expand
Decoding via the API
Shield also provides an API endpoint to decode stack traces from any tool or script:
Endpoint:
GET https://shield.microservice.bytehide.com/api/applications/<project-token>/<protection-secret>?trace=<obfuscated-trace>GET https://shield.microservice.bytehide.com/api/applications/<project-token>/<protection-secret>?trace=<obfuscated-trace><project-token>: Your Project Token<protection-secret>: Your Protection Secret<obfuscated-trace>: The obfuscated stack trace (URL-encoded)
Response codes:
| Code | Meaning |
|---|---|
200 | Original stack trace returned (plain text) |
404 | Application or secret not found |
This makes it easy to integrate deobfuscation into your CI/CD pipeline, crash reporting workflow, or support tools.
Build History
All builds and their mapping files are stored in the Cloud Panel. You can browse previous builds, compare protection configurations, and decode stack traces from any past build:
Click to expand
Related
- Symbol Renaming - The protection that generates mappings
- Cloud Integration - How builds are registered in the cloud