Mobile release gates
Permission denial crashes or blanks the screen
The app assumes camera, location or notification permission was granted, and a denial leaves a blank screen or a crash.
Termsstore sandbox (Apple's and Google's test environments where purchases run without real money) · client bundle (the JavaScript your app sends to the browser or ships inside the mobile app; anyone can read it) · verdict (a one-word release result (pass, pass with findings, fail) with the findings and the checklist version behind it)
highseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
Android's docs require graceful degradation on denial and warn that a second denial is permanent; generated code handles the granted branch.
On Android 6.0 and later, dangerous permissions are requested at runtime; if the user denies, the app must degrade gracefully and keep working without that data; after more than one denial the system stops showing the prompt, which counts as a permanent denial.
How we detect it
Deny each permission at the prompt and permanently, then use the feature.
Most associated with
Tools: Cursor, GitHub Copilot, Claude Code, Windsurf, Lovable, Bolt
Stacks: React Native, Expo
Checklist items that catch it
Permission denial paths are handled
manual Deny each requested permission at the prompt and again permanently; use the feature that needs it.
The app continues with reduced function and explains what is unavailable; no crash or blank screen on any denial.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in mobile release gates
- critical
- high
- high
- high
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.