Release Blockers
Use this when a store, installer, updater, or review flow blocks release.
| Symptom | Likely cause | Fastest next step |
|---|---|---|
| Play rejects upload | Duplicate/lower version code, wrong package name, signing mismatch | Compare package ID, version code, upload key, and Play App Signing status |
| Play production unavailable | Account-specific testing requirement or incomplete app setup | Check Play Console dashboard requirements and testing status |
| Data safety rejected | Declaration does not match app or SDK behavior | Rebuild data inventory from code, SDKs, network calls, and privacy policy |
| Target API warning | App targets below current Play requirement | Update target SDK and rerun release regression tests |
| Screenshots rejected | Wrong dimensions, misleading content, unsupported device family | Re-capture from release build and match store asset guidance |
| Microsoft Store certification fails | Security, technical compliance, content compliance, or policy issue | Read certification report, fix exact failed test, resubmit package |
| MSIX install fails | Package identity, certificate trust, dependency, or architecture mismatch | Inspect manifest, signing cert, dependencies, and Windows event logs |
| SmartScreen warns | New/unsigned download, low publisher reputation, suspicious URL path | Verify signature, test real URL, submit false positive if appropriate |
| Defender flags release | Heuristic or malware scan finding | Rebuild on clean machine, verify dependencies, submit sample for review |
| Tauri update rejected | Bad updater signature or metadata | Verify public key, signed artifact, endpoint JSON, and TLS endpoint |
| Electron update does nothing | Wrong target, missing metadata, publish provider issue | Confirm target supports updater and previous version can reach metadata |
| TWA opens browser chrome | Digital Asset Links verification failed | Verify package name and Play signing certificate fingerprint |
| Apple review asks for info | Missing test account, unclear feature, privacy mismatch | Reply with exact credentials, reproduction steps, and corrected metadata |
Debug Order
- Confirm the artifact identity: package name, bundle ID, Store identity, version code, build number.
- Confirm signing: certificate, upload key, app signing key, updater key, timestamp.
- Confirm store metadata: listing assets, privacy, age rating, policy declarations.
- Reproduce on a clean device or VM using the real distribution path.
- Fix the exact failed gate. Do not resubmit speculative changes.
Gotcha: Most release blockers are identity mismatches or policy mismatches. Rebuilding the app without checking identity, signing, and metadata usually wastes time.