Pre-submit crash and stability checklist
Cold start, first permissions, post-login main path, low-end devices and weak network smoke; common crash sources and logs for review notes. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
Stability rejections are often one line: “crashes on launch” or “crashes when tapping X.” Without low-end device + cold start + weak network smoke, review becomes free QA. Goee (goee.cc) ties crash precheck to precheck scorecard. Buffer with TestFlight tips; after reject rejection fix. Symbolicated crash thresholds per official pages.
What this guide solves
- Release vs Debug differences (asserts, log macros left on).
- Permission bursts on first install unhandled states.
- Main-thread network timeout → watchdog kill.
- OOM on 32-bit / low RAM devices invisible on dev phones.
- Hotfix / remote config empty JSON unguarded.
- New OS APIs while claiming old min OS.
Who should read
| Role | Action |
|---|---|
| Engineering | Fix crashes; export dSYM / mapping |
| QA | Run smoke matrix; log device/OS |
| Listing | Summarize “tested environments” on internal submit sheet |
| Lead | Red line: incomplete smoke → no Submit |
Major releases, arch changes, SDK bumps, login/payment changes → full matrix rerun.
Core practice
Smoke path matrix
| Scenario | Min runs | Watch |
|---|---|---|
| Cold start | 10 | Splash, first dialogs |
| Fresh install | 3 | Keychain, onboarding |
| Upgrade install | 3 | Migration, DB upgrade |
| Login main path | 5 | Empty vs data account |
| Pay / subscribe | 3 | Sandbox |
| Foreground/background | 10 | Camera, AV teardown |
| Weak / offline net | 5 | Timeout UI, retry |
| Low storage | 2 | Cache write fail |
| System language | 2 | RTL, missing strings |
| Dark mode | 2 | Missing assets |
Device tiers
| Tier | Direction |
|---|---|
| A | Current flagship, latest OS |
| B | ~2yo mid-range, N-1 OS |
| C | Minimum supported OS on real device (note sim limits) |
Simulator-only insufficient; camera, push, Bluetooth need device.
Quick crash sources
| Source | Clue | Fix direction |
|---|---|---|
| Force unwrap | FatalError, ! |
Safe optional |
| Main-thread IO | Lag then kill | Async |
| KVO/notifications | Double register | Lifecycle pairs |
| WebView | JS bridge nil | Guards, version isolate |
| Third-party SDK | Init order | Release notes |
| Permissions | Camera nil | Plist + runtime |
Copy-paste templates
Pre-submit stability log
Version / build:
Tester:
Date:
Devices:
1) [model] [OS] — cold start 10/10 OK
2) [model] [OS] — login OK, issues: none
Weak net: Charles 3G 5% loss — OK
Upgrade: from vX.Y over-install — OK
Known open: none / [#ticket, non-blocking reason]
Symbols uploaded ASC/Play: Y/N
Review notes (environment-dependent only)
Tested iPhone [model] iOS [version] and [Android model] API [level].
First launch: Location denied — app usable.
If map tiles slow on 3G, wait 10s; no crash.
Common mistakes
- Debug-signed build only—test Release matching submit.
- Ignore crash after first reject—reviewer path ≠ QA; notes cover delta.
- Firebase rate only—zero samples on new feature still smoke.
- No symbols uploaded—cannot symbolicate ≠ no problem.
- Hotfix during review—freeze build under review.
- Network fail as acceptable crash—graceful degradation required.
FAQ
Play pre-launch report replaces smoke?
Helpful not sufficient—run main paths yourself.
TestFlight clean = ship?
Narrow beta paths—matrix again before production submit.
iPad crash, never tested iPad?
If iPad supported, test; else fix device capabilities/UI.
Weak net lag = crash?
Not always—but watchdog kill looks like crash to review.
Map rejection codes?
Common rejection codes.
Crashes, symbols, privacy
Crash SDKs upload device IDs and stacks—symbols uploaded, sampling matches disclosure, no debug menu in Release. If user opts out of analytics, crash SDK must not second-crash. OOM on image decode—check assets; map SDK weak-net init timeouts.
Deliverable records
For Goee/client: build fingerprint, tester, date, device table, per-path pass/fail, weak-net params, open issues and submit-go decision sign-off. “Should be fine” ≠ precheck done. Tie to precheck scorecard stability row—proves diligence, not approval.
Hotfix discipline during review
If P0 fixes allowed, document resign same build vs new build resubmit. Do not stack unrelated untested fixes. After reject, full matrix—not only the failed step.
Execution rhythm
Smoke after feature freeze, before screenshots—otherwise shots paths never tested. Phased release: gray tracks use Release config. Pre-launch report + Firebase supplement, not replace human matrix. Checklist blocks “YOLO submit.”
Rejection keyword mapping
| Letter phrase | Retest first |
|---|---|
| launch crash | Cold start × low RAM |
| tap X | Control × permission denied |
| iPad | Layout × split screen |
| payment | Sandbox × offline |
Archive smoke log one quarter after version fully offline.
AV/map/AR separate rows—permission deny native crashes common. CI UI tests help; release candidate still needs device sign-off. Monthly retro vs common rejection codes stability items.
TestFlight external feedback
External devices find crashes outside matrix—feed back new device/scenario rows. Production notes: “Beta issue #xxx fixed in this build.” Do not ship formal review with open P1 launch crashes.
Sign-off block
Stability owner: ______ date: ______
No open launch-crash tickets: Y/N
Submit build = tested build: Y/N
Internal review and boundaries
Listing is delivery, not legal final—official pages. Defect vs wording. Telegram @hagee66 with build and checklist. No approval promise; no hidden features or dual binaries.
| Check | Goee | Client |
|---|---|---|
| Path/notes | Yes | Demo account |
| Policy URL | Yes | DNS |
| Forms vs package | Verify | SDK table |
| Legal | No | Counsel |
Next steps
Merge smoke into precheck scorecard. Matrix or rejection help: Telegram @hagee66. No approval promise—verify log completeness.
Back to guide library · Apple listing · Google listing