The project owner confirms that PyBLE is published on Google Play. Current first-party README and website copy still described an invited Android internal test, while the public store listing described open testing.
The official Google Play listing
was retrieved over HTTPS on 2026-09-25 with English/US presentation parameters
(hl=en&gl=US). It returned HTTP 200 and identified SciLabPro, app version
0.2.0, and release notes stating “Open testing for PyBLE 0.2.0.” The
package is dev.pyble.pyble. This primary-source result supports the
owner-confirmed publication and supersedes the invited internal-testing copy.
The AppAgg entry also lists version 0.2.0 and the same open-testing release notes, with a 2026-09-16 listing date. It is corroborating third-party indexing, not proof of the exact rollout date or Play Console configuration.
- Describe Android as PyBLE 0.2.0 published on Google Play for open testing.
- Keep iPad described as the external TestFlight beta.
- Link directly to the existing official Google Play listing and encode the
same destination in the neutral
/google-play/pyble-google-play-qr.svgasset. - Keep README, home,
/app, metadata, setup guidance, and current distribution documentation consistent. Remove the invitation requirement from current Android installation guidance. - Google Play determines account, country, device, and testing availability. Open testing does not establish a production-track release or universal availability.
The candidate opt-in endpoint redirected to Google sign-in. No signed-in enrollment or on-device installation was verified in this review. The public listing remains the link; no inferred opt-in destination is introduced.
The repository's App source version remains 0.2.0+8. The public app version
0.2.0 does not establish the installed store artifact's version code, source
commit, or inclusion of later connection-lifecycle fixes. The
build-8 handoff and original submission
materials remain historical preparation records. Firmware versions and
qualification evidence remain independent of the app distribution channel.
This record documents availability and the coordinated content contract. It does not attest a deployment, signed-in Play Console state, installed app binary, or hardware-validation result. Search engines control when indexed snippets refresh after updated pages are published.