Engagement
Exports in. Signatures named. Readout on the calendar.
This is the shape of the work, whether you book the fourteen-day crash stability audit or a single OEM bench day. No hosted console. No migration of your crash reporter.
-
Briefing
You send the application ID, the noisy version codes, and what Play Console or your crash reporter is already showing. We reply within two working days with whether an audit, an ANR review, a gate, triage, or a bench day fits — and what access we need. If mapping files are absent, we say the clock cannot start.
-
Access, not a portal
Play Console admin, a time-boxed viewer role, or ZIP/CSV exports. Crashlytics, Bugsnag, or Sentry exports if you use them. Mapping.txt or native symbols for each affected version code. We do not ask you to install an SDK of ours.
-
Clustering
Fatal Java/Kotlin stacks, native tombstones, and ANRs are read as three different objects. OEM and API-level skew is written next to each named cluster. Unknown frames stay unknown; we do not guess class names.
-
Kepong bench, when the cluster needs a handset
If a signature is tied to One UI, HyperOS, ColorOS, Funtouch, or Realme UI, Wei Shan matches a unit on the bench at No. 29 Jln 2/1A Taman Kepong Indah. You may sit in. If we do not hold the model, we say so before the day is booked.
-
Pack and readout
The written pack arrives before the call. The ninety-minute readout (or the shorter ANR/gate call) is with the engineer who read the traces. We do not ship your hotfix. We will sit with your engineers while they decide order.
What you should have on the table
- Application ID and flavour names
- Version codes in the noisy window
- ProGuard/R8 mapping for those version codes
- Unstripped native libraries or symbols, if you ship .so files
- Last two release notes, even if they are messy
- List of devices your testers actually hold
What we will not do in the engagement
We will not merge patches, run your UI automator suite, or take over Play Console releases. We will not describe a vendor WebView crash as your Kotlin bug, or the reverse. If the testing track has almost no testers, a pre-release gate will say the sample is too thin rather than stamp go.