simpletest/who_need_help
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
b639db157c
who_need_help/android/play-store/release-checklist.md

3.3 KiB
Raw Blame History

Google Play release checklist

External account gate

  • Google Play developer identity verification approved.
  • Contact phone verification completed.
  • Play Console enables Create app.

App identity and signing

  • Create Android app Who Need Help with package org.whoneedhelp.mobile.
  • Default language: English (United States).
  • App: not a game; free; no ads.
  • Accept Play App Signing.
  • Record upload-certificate SHA-256 and Play App Signing SHA-256 separately.
  • Add the Play App Signing SHA-256 to production Google/Firebase Android configuration.
  • Publish and verify https://whoneedhelp.com/.well-known/assetlinks.json for the Play certificate.

Build

  • Build from the exact committed candidate with the validated Android allow-list read from the production checkout’s single .env.
  • Run scripts/android-release-build.sh.
  • Verify source fingerprint, signing certificate, bundletool validation, lint, package name, version code/name, target SDK, and production origin.
  • Install the universal APK generated from the same AAB on the authorized physical phone and run the release smoke test.
  • Upload the source-bound AAB first to internal testing.

Store presence

  • 512×512 Play icon prepared.
  • 1024×500 24-bit PNG feature graphic prepared.
  • Four current 1080×1920 physical-phone screenshots captured and reviewed.
  • English, Ukrainian, and Russian listing copy prepared.
  • Alt-text copy (≤140 characters) prepared in store-assets/README.md.
  • Enter the prepared alt text when the assets are uploaded in Play Console.
  • Choose category/tags in the current Console options.

App content

  • Privacy policy URL.
  • Ads declaration: no ads.
  • App access instructions tested from a clean install.
  • Target audience/adult-only positioning confirmed.
  • Content rating questionnaire completed truthfully.
  • Data Safety worksheet reconciled with the final dependency report.
  • Account deletion questions and external URL completed.
  • Government/news/financial/health declarations answered from actual app behavior; do not describe the app as a medical service.
  • Foreground-service/location declarations completed if Play Console asks.

Testing

  • Internal track smoke test passed.
  • Closed track created and opt-in link tested.
  • At least 12 testers continuously opted in for 14 days.
  • Tester feedback and fixes documented.
  • Production-access questionnaire completed from actual evidence.

Publishing

  • Managed publishing enabled if desired.
  • Countries/regions and support contact reviewed.
  • Production submission reviewed for accidental test URLs or credentials.
  • Rollback and support/incident response are ready.

Official references: