I am still getting the following message sometimes in version 6. Moviebase always starts successfully on the next try after I receive this message so clearly Google Play is running. I sill think the problem is probably too low a timeout value waiting for Google Play to respond.
It’s weird, I have never seen another user with this issue in either of my apps (1m users per month).
Here are the most common issues:
- De-Googled Devices or Custom ROMs: The user is running a privacy-focused OS (like GrapheneOS or CalyxOS) or an unsupported device (like an Amazon Fire tablet or newer Huawei devices) that doesn’t have Google Play Services installed natively.
- Sideloading / Third-Party Stores: The user downloaded the app from outside the official Play Store (e.g., via the Aurora Store, F-Droid, or an APK site). The app is pinging Google Play to verify the license/purchase or run a Play Integrity check, and failing because Google Play didn’t handle the installation.
- Disabled Services: The user manually disabled the Google Play Store or Google Play Services in their Android settings to save battery or data.
- Corrupted Cache/Data: The device has a legitimate version of Google Play, but the app’s cache or the Play Store’s background services are glitching and failing to authenticate.
None of those apply to me as far as I know. I’m running a Samsung S22 with standard Android 16. No special ROM or side-loaded apps running. It doesn’t happen often. It has only happened twice on version 16 so far. To recover I just close the message and try again. It always works on the second try. Over 1M users is impressive. It’s a great app. I’m glad it has been so successful for you.
Of course it is also possible that some others have had the problem but didn’t take the time to report it. Anyway, I thought you would want to know it was happening. Obviously, I have opened the app many times. Two occurrences in all those is not many, and some wouldn’t take the time to report it, since it usually works and it works on the second try even when the error does occur.
That’s true. I can try to add some improvements to the libraries. It’s something which comes from Google directly.
