Readable stack traces
A shipped build reports stacks with minified or obfuscated names. Upload the source maps or symbol files for that build and Ravensight shows each error's stack the way you wrote it: your file, line and function beside every line a file could map. The raw stack your players' devices sent is always shown too, and each mapped line is marked as symbolicated. Stacks are read when you open an error, never when the event arrives, so a file uploaded today also fixes yesterday's errors from that build.
File kinds and matching
| Kind | File | What it does |
|---|---|---|
sourcemap | A version 3 JavaScript source map, plain or indexed | Maps a minified frame's line and column to the original file, line, column and name. Name the map after its bundle (game.min.js.map for game.min.js); a build with one map uses it for every bundle. |
android_mapping | The R8 or ProGuard mapping.txt | Retraces class and method names, and the original line where the mapping records line ranges. Where inlining leaves more than one candidate, all are named. |
breakpad | A Breakpad .sym text file | Maps module+0xoffset frames to the function, and the source file and line from its line records. Name it after the module (libgame.so.sym). |
dsym | A dSYM bundle, zipped | Stored and listed so it is ready; it is not read yet. Apple symbolication comes in a later release. |
Files are matched to the game_version your game reports, so upload them with exactly that build string. Each file is checked when it arrives, and a file that is not the kind it claims is refused before anything is stored or charged.
Limits, price and who uploads
Limits: 50 MB a file, 500 MB and 50 files a build. Ravensight keeps the newest 10 builds of each game (a build's age is its newest upload), and each file for 90 days; the hourly sweep deletes anything past either limit. Deleting the game deletes its files.
Price: 10,000 weighted events per started megabyte (1,000,000 bytes) a month, on the same event meter as everything else: the included events first, then prepaid balance, which is $0.005 a megabyte-month. Every file rounds up to a whole started megabyte, in every month: two 1 KB files are 2 MB. An upload pays its own month when it arrives. Each later month, the files uploaded before that month and still kept are counted for the game, each rounded up. No month is charged while the game is inactive or its error capture is off, and stacks are shown raw meanwhile; the files still expire on schedule. A part month counts as a whole month and nothing is prorated, as with extended retention. Reading stacks and listing files is free, and deleting a file refunds nothing. A game at every limit is at most 5,490 started megabytes, $27.45 a month.
| Stored | Weighted events a month | After included events |
|---|---|---|
| One 2.4 MB source map | 30,000 | $0.015 |
| 10 builds of one 40 MB file | 4,000,000 | $2.00 |
| 10 builds of one 500 MB file | 50,000,000 | $25.00 |
Funding: uploading needs a funded prepaid balance. With an empty balance an upload is refused with 402 needs_funds, and nothing is stored or charged. If a later month's payment is refused, the owner is emailed, and the game has 14 days from that notice to add funds; nothing is deleted until the notice has been sent. After that the month is not pursued and its symbol files are deleted, except files uploaded in the current month, which their upload already paid for.
Who: only the studio owner uploads and deletes, because every stored megabyte is billed each month. Every member who can read errors sees the list with sizes and monthly cost, in the Symbol files section under Errors. A studio a game is shared with never sees its symbol files and reads raw stacks only. Uploads are never available as an MCP tool; list_symbol_files reads the list, and get_error_issue returns the symbolicated lines.
Upload
Upload from a build script
curl -X POST \ -H "Authorization: Bearer $RAVENSIGHT_TOKEN" \ -H "Content-Type: application/octet-stream" \ --data-binary @dist/game.min.js.map \ "https://api.ravensight.io/api/v1/games/<gameId>/symbols?build=1.4.1&kind=sourcemap&name=game.min.js.map&recurringConsent=true"
The token is the owner's CLI token (gt_cli_, from ravensight-playtest login) with the playtest:upload scope; the dashboard session works too. recurringConsent=true authorizes the monthly charge and is required. name is 1 to 200 letters, digits, dots, underscores, at signs, plus signs or hyphens.
| Status | Error | Meaning |
|---|---|---|
| 201 | Stored. charged gives the megabytes and weighted events paid for this month. | |
| 200 | The same bytes were already stored for this build. duplicate is true and nothing was charged. | |
| 400 | invalid_build, invalid_kind, invalid_name, empty_file, invalid_symbol_file, recurring_consent_required | Fix the request; nothing was stored or charged. |
| 402 | needs_funds | Add prepaid balance; nothing was stored or charged. |
| 403 | forbidden, insufficient_scope | Not the owner, or the CLI token lacks playtest:upload. |
| 429 | usage_backstop | The account reached its monthly usage safety limit; nothing was stored or charged. |
| 409 | symbol_file_exists, too_many_files | Another file has this name and kind in the build (delete it first), or the build holds 50 files. |
| 413 | file_too_large, build_too_large | Over 50 MB a file or 500 MB a build. |
| 503 | symbols_unavailable, billing_unavailable, symbol_storage_unavailable | Storage or billing is not available. A storage failure during upload is refunded. |
List and delete
GET /api/v1/games/{gameId}/symbols lists builds and files with sizes, the monthly events and the deletion dates. DELETE /api/v1/games/{gameId}/symbols/{fileId} deletes one file (owner only). Another studio's game answers 404.