APPSINITYCrash reports
There is no crash reporting on Appsinity. No SDK is shipped, no stack trace is stored, no ANR is grouped, and Studio has no crash screen. This page documents the absence so you do not look for a dashboard that was never built.
Open Appsinity StudioThe state, precisely
| Capability | Exists? | Detail |
|---|---|---|
| Crash SDK provided | No | Nothing is bundled with a build |
| Crash dashboard in Studio | No | There is no such screen or tab |
| Stack trace storage | No | No table holds traces |
| ANR detection | No | Not measured at all |
| Crash-free users metric | No | No denominator exists to compute it |
| Symbol upload | No | No mapping files are accepted |
| Player-submitted crash report | No | There is no report button on a listing |
| Developer log capture | No | Nothing runs inside your process |
| A data-safety category for crashes | Yes | collectsCrashLogs is one of the eleven |
collectsCrashLogs row exists because players need to know when a third-party reporter ships traces. It is a disclosure field, not a feature. Ticking it does not turn anything on.Do it yourself
- Pick a reporter. Any crash SDK for Android, or a browser error handler for a web build.
- Keep traces on your infrastructure. You are the controller of that data; Appsinity is not a processor of it.
- Declare it. Set
collectsCrashLogsandcollectsDeviceInfoto collected, and name the SDK in the disclosure. - Publish a real support email. It is the only inbound channel a player has for a crash, see Contact support.
- Mention known issues in the listing. A long description that names a device quirk stops it becoming a one-star review.
What you can still see here
- Play sessions tell you whether engagement collapses after a release; a sharp drop in average play seconds is the closest proxy for breakage.
- Rating average and the newest reviews are a crude crash signal, and the read covers the hundred most recently updated rows.
- The download counter tells you whether a bad build is still being taken, which is how you decide whether to unpublish fast.
- Traffic by country and source tells you whether a regression is regional or global.
Desktop client failures
The Windows client installs and launches titles from a local library. When a launch fails, the failure is on the player's machine: the client keeps a bounded local log and nothing is uploaded.
- A corrupt archive in
%LOCALAPPDATA%\Appsinity\library\<slug>is fixed by deleting that directory and re-installing. - A Windows release that is only an installer EXE inside a ZIP will not launch through the client's extract-and-run path; ship the game directory.
- The client never publishes anything, so a broken listing is always fixed in Studio, not there.
Frequently asked questions
Where is the crash dashboard?
It does not exist. Appsinity has no crash collection and no crash screen; the data-safety row is a declaration only.
Do you at least get error logs from the store?
No. Platform usage logs record requests and failures of the platform itself, never anything about your game's runtime.
Can players report a crash to me?
Through your published support email and through a review. There is no report button on a listing.
Does the automated scan catch a crashing build?
No. The scan checks file extensions and names; a build that crashes on launch is entirely invisible to it, see Malware policy.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]