Mobile release release incidents

Mobile release: 6 published incident types backed by 15 public reports.

The root-cause stage named most often in this group is release-process, in 4 of 6 incident types.

6 incident types published · 2 withheld · 15 public reports

Incident types in this group

Mobile release


API version dropped while old app live	Likelihood: not published (1 public report in 5 years)	Impact: medium (2 of 2 reports: availability)	2
App store rollback not possible	Likelihood: medium (5 public reports in 5 years)	Impact: medium (2 of 5 reports: availability)	5
Crash on older OS version	Likelihood: low (2 public reports in 5 years)	Impact: medium (2 of 2 reports: availability)	2
Deep link broken after routing change	Likelihood: low (2 public reports in 5 years)	Impact: medium (2 of 2 reports: availability)	2
In-app purchase receipt validation fails	Likelihood: low (2 public reports in 5 years)	Impact: high (2 of 2 reports: money)	2
Push notification token reset	Likelihood: low (2 public reports in 5 years)	Impact: medium (2 of 2 reports: availability)	2

Withheld in this group: Forced update locks users out, Offline sync conflict after schema change. Reasons per route

Risk grid

Risk grid: count of incident types per likelihood and impact cell, from data/risk.json
Likelihood \ Impact	Impact: high	Impact: medium	Impact: low
Likelihood: high	0	0	0
Likelihood: medium	0	1	0
Likelihood: low	1	3	0
Impact unrated or likelihood not graded	1

Table equivalent: incidents per cell

Incident	Likelihood	Impact
API version dropped while old app live	not-published	medium
App store rollback not possible	medium	medium
Crash on older OS version	low	medium
Deep link broken after routing change	low	medium
In-app purchase receipt validation fails	low	high
Push notification token reset	low	medium

Root-cause stages

Stage	Incident types naming it
release-process	4
code	3
config	2
build	1
infra	1
third-party	1

Fewer than 2 reports in this group state both the change time and the detection time; no median is printed.

Only on this page

Crash on older OS version is the incident type in this group whose root causes do not include the release-process stage; its causes are introduced at code and build.

Group checklist

The first pre-release item of each published incident type in the group.

GR-01API version dropped while old app live: Keep one contract test per client version still in distribution, including each old command-line release, and run all of them against the API before a version retirement takes effect. contract
GR-02App store rollback not possible: Open an email login link on the iOS release build and confirm the link completes sign-in. e2e
GR-03Crash on older OS version: Launch the exact binary submitted to the store on a device running iOS 16 and confirm the app reaches its first screen. compatibility
GR-04Deep link broken after routing change: Before a domain migration, request the site association file on the old domain and confirm it is served directly with no redirect. config
GR-05In-app purchase receipt validation fails: After any in-app purchase plugin upgrade, make a sandbox purchase on a supported iOS device and confirm the server validates the serverVerificationData it receives. integration
GR-06Push notification token reset: Send a test push through the new push backend for two apps that share one p8 push configuration and confirm both apps' valid device tokens are accepted. integration

Questions

What causes Mobile release incidents?

Published incident types in this group name these root-cause stages: release-process (4), code (3), config (2), build (1), infra (1), third-party (1).

Which pipeline stage introduces most Mobile release incidents?

The release-process stage, named in 4 of 6 published incident types in the group.

Which test classes catch Mobile release incidents?

Test classes listed on the group's incident pages: synthetic monitoring (3), end-to-end tests (3), canary and progressive delivery checks (3), contract tests (2), configuration and environment tests (2), integration tests (2), compatibility tests (1).

How quickly are Mobile release incidents detected in public reports?

Fewer than 2 reports in this group state both the change time and the detection time, so no median is published.

How likely are Mobile release incidents compared with each other?

API version dropped while old app live: not-published likelihood, medium impact; App store rollback not possible: medium likelihood, medium impact; Crash on older OS version: low likelihood, medium impact; Deep link broken after routing change: low likelihood, medium impact; In-app purchase receipt validation fails: low likelihood, high impact; Push notification token reset: low likelihood, medium impact.

What should a release checklist for Mobile release include?

The group checklist collects the first pre-release item of each of the 6 published incident types; each item names the test class that checks it.