OK Rummy v1.4 install: signature and source checks.
v1.4 · Install signature refresh
The OK Rummy v1.4 APK shipped this week with a refreshed install signature and a stricter source check on the install confirmation screen. The change is invisible to most installers - the install still completes with a single tap - but it does two things that matter: it confirms the file came from the first-party access surface, and it blocks any APK that was modified after the brand team signed it.
What changed in v1.4
Three things changed in the v1.4 release. The APK is now signed with a v2 and v3 signature instead of v1 only, which is the standard for Android 9 and above. The install confirmation screen now lists the package name and the source of the file next to the install button. And the in-app version screen shows the SHA-256 hash of the installed file, so the support team can verify a clean install without screenshots.
The v2 and v3 signatures are deterministic - the same APK always produces the same hash, so a hash mismatch is unambiguous evidence of a tampered file. The v1 signature alone is still accepted by Android 7 and below, but those Android versions are no longer in the supported list; the v1 signature is now the fallback for legacy devices that have not received an OS update in years.
What this means for first-time installers
If you are installing OK Rummy for the first time, nothing changes. Tap Install App below, allow the source for the current session, and tap Install. The install completes in a few seconds. The new source check on the confirmation screen will show the package name and the source URL - confirm they match com.okrummy.app and getokrummy.com before tapping Install.
What this means for existing installers
Existing installers will see the v1.4 update through the standard Android update flow. If your device blocks the update, the cause is almost always one of two things: the device is on Android 7 or earlier, or the device has the v1.3 install with a signature that does not chain to v1.4. The first case is not in the supported list; the second case is fixed by uninstalling v1.3 and installing v1.4 from the verified surface.
Players who installed a v1.3 APK from a non-first-party source - a forwarded link, a search-result link, a third-party app store - will see a signature mismatch on the install confirmation screen. The correct response is to remove the v1.3 install completely (Settings → Apps → OK Rummy → Uninstall) and to start the v1.4 install from this product profile. The verified surface is the only source that holds the v1.4 signing key.
How to confirm a clean install
Open the app, tap the profile icon in the top-right corner, and choose About. The version screen lists the version, the build, the signature, and the SHA-256 hash. The hash on the screen should match the hash on the install confirmation screen; if it does not, the install is not from the first-party access surface and should be removed.
What to do if the install is rejected
The four-step path in /setup/ covers the most common rejection causes. The path is short and reversible: clear the old install, allow the source for the current session, re-download the file, and free storage. If the path does not resolve the issue, the support chat at /contact/ can confirm whether the install reached the access surface and whether your device matches the published requirements.
The next release is scheduled for mid-September and will refresh the wallet verification flow. The changelog will be posted in /news/ the same day the release ships.
What we are watching
The next item on the team's watchlist is the Android 14 unknown-source prompt, which is currently expected to keep the same wording as Android 13. The setup guide at /setup/ is updated in the same week as any Android-side change; the /news/ hub carries the announcement. If a release breaks the install path on a specific device, the support chat at /contact/ is the fastest way to get a response from the team - keep the chat window open and the team replies in the same window.