Latest build version, in plain language.
Where the latest version is published and what an adult reader should verify before signing in on an older build.
Notes on the latest app build.
The platform publishes the latest build version in the release notes. The version, the size, the hash and the release date are platform-defined. This page documents where to find them.
Where the version is published
The platform's release notes are accessible from the Help centre or from the in-app settings. The release notes list the version number, the file size, the hash and the release date. The latest version is also visible in the app-store listing under the platform's published name.
What an adult reader can verify
- Open the app and check the version listed in the About section.
- Open the app-store listing and check the version number.
- If they differ, the reading should favour the app-store listing as the published reference.
If you are running an older build
Most regulated platforms allow older builds for a short grace period. The grace period is published in the release notes. Once the grace period expires, the older build stops receiving deposits or withdrawals; update at the next opportunity.
How to be notified of a new build.
Most regulated platforms publish a release-note notification mechanism: an in-app alert on the next sign-in, an email to the registered address or a push notification if the reader has opted in. The mechanism is described in the platform's Help centre. The reader who wants to be notified of new builds should confirm at least one mechanism is active before relying on it.
The grace period
The grace period is the period during which an older build can still be used. The grace period is published in the release notes; common values are 14, 30 and 90 days. The reader who is on a build older than the published grace period may face a sign-in block or a reduced feature set.
When an update breaks a feature
When a new build introduces a regression, the platform publishes a hotfix quickly (commonly within 24 to 72 hours). The reader who reports the regression via customer-care gets the hotfix notification. The reader who cannot upgrade is typically accommodated by a manual fallback during the grace period.
What the build version actually means.
The build version is a semantic tag that identifies the platform's mobile app build. The version uses a major.minor.patch convention: the major version is incremented at a breaking change; the minor version is incremented at a feature addition; the patch version is incremented at a hotfix. The platform's release notes describe which kind of change each version represents.
Where to find the version
The version is published in three places: the in-app About section, the app-store listing and the release notes. The three values should match. If they differ, the app-store listing is the published reference because the platform controls the app-store listing more tightly than the in-app display.
The hash and the size
The build's file hash (sha256) and file size are published alongside the version in the release notes. The hash is a fingerprint that uniquely identifies the build's bytes; comparing the hash against the downloaded file confirms the file is unmodified. The size is a sanity check; the size should match what the platform publishes.
Why the version matters
The version matters because each build may include a regression that the reader needs to be aware of. A reader who has a problem on build 4.2.1 may find that the platform has hot-fixed the problem in 4.2.2. The release notes describe the hotfix; the reader can update to the new build to receive the hotfix.
The grace period
The grace period is the window during which an older build can still be used. Most regulated platforms offer a 14 to 90 day grace period. After the grace period expires, the older build stops receiving deposits or withdrawals and may stop signing in altogether. The reader who is on an older build should update at the next opportunity.
How to update
The update is issued through the platform's update channel: the App Store on iOS, the Play store on Android, or the in-app updater. The reader should confirm the update channel is enabled, allow the platform's notifications, and update within the grace period.
What happens when a build is migrated.
A build is migrated when the platform switches from one release to the next. The migration is the window during which the older build and the newer build can coexist on the platform's update channel. The reader can run either build during the migration window; the platform typically defaults to the newer build once the older build's grace period expires.
Reading the migration plan
The migration plan is published in the release notes. The plan lists the start date of the migration, the end date of the grace period, the schema changes between the older and newer builds, and the recommended transition steps for the reader. The reader who reads the migration plan can plan the update accordingly.
How to migrate cleanly
The cleanest migration is during the grace period: update within the first 7 days of the grace period, confirm the new build's controls match the older build's controls, and contact the platform's customer-care pathway if any feature behaves differently. The reader who waits past the grace period may face a forced update at next sign-in.
What happens after the grace period
After the grace period expires, the older build stops signing in. The reader is forced to update to the newer build. The forced update is not a sign of trouble; it is part of the platform's lifecycle management.
What the publication does
The publication describes the migration pattern an adult reader should expect. The publication does not track specific version numbers; the platform tracks those. The reader who wants the latest version should consult the platform's release notes.