Guide summary
Check Android package registration for Thailand after the first developer verification phase began on September 30, 2026.
For: App portfolio owners and release managers with Thailand distribution.
Release sequence
- Inventory the Thailand listings that use participating stores and note the artifact source for each.
- Capture the final application ID and normalize the SHA-256 fingerprint from each delivered production APK.
- Check every package-and-certificate pair and assign each unresolved console action to an owner.
- Prepare Thai-language support notes and recheck after a package, signing or distribution-channel change.
Quick facts
PkgReady checks the values submitted to it; it cannot discover which artifact a store delivered. Keep evidence for each channel, and treat the 2027 global expansion as planned future scope rather than current coverage.
Detailed guidance
Keep Thailand release evidence current
The first phase has been in effect in Thailand since September 30, 2026 for installations from participating stores on certified Android 7 or higher devices. Keep the artifact, package, certificate, console result and checked time together so support can tell which release a status applies to.
After a signing or channel migration, inspect the new production APK and run the check again; an older passing result does not establish the new artifact's identity. Android describes broader rollout as a 2027-and-beyond step, so use official guidance to update the country scope as it changes.
- Retain the full SHA-256 fingerprint and artifact version.
- Assign every unresolved result to a release owner.
- Recheck after a key, package or channel change.
- Prepare Thai-language support notes that distinguish registration from store review.
Have the production package name and signing certificate ready? Query the official registration state, then use the result to choose your next step.
Run status check →Frequently asked questions
Is Thailand the end of the program?
No. Thailand is in the first four-country phase. Android's current guide describes broader expansion to apps on certified devices in 2027 and beyond; it does not make that future scope part of today's regional first phase.
Can PkgReady discover every store artifact automatically?
No. The check uses the package name and optional public SHA-256 fingerprint you submit. Your team must identify the relevant store build and inspect its production artifact.
Sources and review
Last reviewed: