Reference
Troubleshooting
Common problems when protecting a file: rejected symbols, the program does not start after protection, runs slower, limit reached, API errors.
The panel rejects the symbols
The symbols come from a different build than the file. Build the file and its symbols again in one step and upload both. The symbol files page explains how matching works.
The program does not start after protection
- Check that protection does not cover functions with inline assembly. Set their level to
none. - Lower the level of functions that run very early, such as constructors of global objects.
- If the problem remains, choose Report a problem on the job in the panel. We attach the processing log to the report, so you do not need to upload the file again.
The program runs slower
The usual cause is virtualization of a function called in a loop. Set it to mutation or none and compare timings in a profiler. The protection settings page explains how to choose a level.
The daily limit is used up
The limit renews 24 hours after the first protection in the window. The panel shows the renewal time, and the API returns it in the resets_at field. The limits and queue page explains how the limit is counted.
The API responds with 403
The token is valid, but the account’s plan does not include the API. API access is included in Pipeline and Foundry. The other error codes are on the API page.
Note
When reporting a problem, include the job id from the panel, for example prt_7Hq2Lx. The support address is on the Support page.