Steps
Force close Genify and reopen the app.
Confirm you are using the latest app version available to you.
If you installed the app from Google Play, uninstall and reinstall it from the same Play testing track or production listing.
If you installed a local test build, ask the developer to register the Firebase App Check debug token for that device.
If the issue continues, contact support with your Android model, app version, and a screenshot of the message.
For regular app users
This error usually means the app could not complete device verification. Updating, reinstalling from Google Play, and using a stable network usually resolves it.
Avoid installing old APK files from outside the official testing or production channel because those builds may not match the current verification setup.
For testers and developers
Local Android builds may use Firebase App Check debug mode. In that case, the device debug token must be added in Firebase Console before sign-in will work.
Release builds should use Play Integrity. Firebase must have the Android package name and the correct SHA-256 signing certificate for the build source, including Play App Signing when testing through Google Play.
Common fixes
Use the same install source consistently: Android Studio, internal testing, closed testing, or production.
Register the App Check debug token for local debug builds.
Add the Play App Signing SHA-256 certificate in Firebase for Play-distributed builds.
Rebuild and reinstall the app after changing native App Check environment settings.
Frequently asked questions
Is this a password problem?
Usually no. This error happens before or during app verification, not because your password is wrong.
Why does the message mention a browser on Android?
Genify uses a shared verification message across web and mobile. On Android, it means native app verification failed.