The Problems page
What your app's Problems tab shows: each failure learners ran into, where and why it happened, and what you can do about it.
Each app's page under Apps has a Problems tab. It lists the failures the app's learners ran into, as the SDK reported them (Errors in 4.0): where it failed, why, and what the device could do. Most learners never write to say that something failed. This tab is how you find out, and fix it before more of them hit it.
What it shows
Reports of the same failure are one problem: the same stage, reason, code and HTTP status. Problems are listed newest first, and each one shows:
- Where and why. The stage (Settings, Registration, Attestation, Model key, Manifest, Download, Verification, Storage, Engine start, Opening the model, Accelerator, Microphone and audio, Recognition, Sharing, Analytics), the code your app got, the reason and the HTTP status.
- What happened, and what you can do, in plain words, in English, Indonesian and Arabic.
- How much. Installs (approximate), reports (one per install and day), the times it happened, first and last seen, how many reports came from an install's first launch, and how many had the SDK try again inside the call.
- The last 14 days, one bar a day.
- Where it happened. Browsers, systems or device models; SDK, app and model versions; the platform's error codes. A value seen in fewer than 10 reports is not named, except the SDK and app versions.
- What stands out. A capability most of the reports share: a page that is not cross-origin isolated, no WebAssembly SIMD, little memory or free storage, a 32 bit process.
A web key's origins are one app, as on the Issues tab, and you can look at one origin. Problems reported with the development key are listed apart and never counted with production. The app's Overview shows how many problems there are and the newest three.
Silent problems
Some problems are marked silent: your app was not told, and the SDK went on in a lesser way. For example, storage the browser blocks, so the model is downloaded at every visit, an expired lease opened in its grace because Quran Lab could not be reached (Offline use and the lease), or a web lease given without a clear answer of the invisible bot check. Nothing failed for the learner yet, but they show what to fix before it does.
Why it is there
A failure that only your app's learners hit is often something only you can fix: an origin your web key does not list, a page whose Content-Security-Policy blocks Quran Lab's frame, a release of your app that dropped a permission, phones that run out of memory. Quran Lab sees the same reports across every app, and uses them to find and fix what is wrong in the SDKs and on its servers.
When a problem looks like Quran Lab's side, report it, or ask your coding assistant to tell Quran Lab.
What it never shows
No report carries audio, what the model heard, a name or an identifier of a learner, an install or a device. You see counts, versions and what the devices could do.
Which SDKs report
SDK 4.0 on every platform, and the newest 3.x patches for the web and Android. An app on an older SDK has an empty tab, which does not mean that nothing failed. Older issue reports keep their own Issues tab.