Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Flutter phone sign-in fails with status 17028 and play_integrity_token

ErrorSMS verification code request failed: unknown status code: 17028 Invalid request fields in play_integrity_token

Short answer

Firebase checks the app with Play Integrity before sending an SMS, and that check needs your SHA-256 fingerprint. Add SHA-256 for every key that signs the app, including the Play App Signing key if you use it. If the check falls back to reCAPTCHA, it needs SHA-1 and an API key that is not restricted.

  • Applies to Flutter 3.x, firebase_auth 5.x, Android
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the fingerprints of the key that signed the build you are running, then compare them with the Android app in the Firebase console.

    cd android
    ./gradlew signingReport
  2. 2Match what you see, then jump to its fix

    1. 117028 on a debug or release build; only SHA-1 is listed in the consoleThe SHA-256 fingerprint is not registeredFix
    2. 2Your own fingerprints are registered, but the build you test is signed by Google PlayThe build is signed with a key you did not register (Play App Signing)Fix
    3. 3Play Integrity cannot verify the device, and the browser step fails or never returnsThe reCAPTCHA fallback cannot completeFix

What does the error look like?

  • SMS verification code request failed: unknown status code: 17028 Invalid request fields in play_integrity_token

Cause 1 of 3

The SHA-256 fingerprint is not registered

1Check

The phone auth guide says to specify the app's SHA-256 fingerprint to use Play Integrity. Compare the SHA-256 line from signingReport with the console.

./gradlew signingReport | grep -E "Variant|SHA-256"

2Fix

In the Firebase console open Project settings, find your Android app and add the SHA-256 (and SHA-1) under SHA certificate fingerprints.

# Firebase console > Project settings > Your apps > Android app > SHA certificate fingerprints > Add fingerprint

3Verify

Rebuild, install and request a code again.

flutter run

Confirmed by firebase.google.com

Did this fix it?

Cause 2 of 3

The build is signed with a key you did not register (Play App Signing)

1Check

With Play App Signing, Google re-signs the app, and its certificate differs from the upload key you create locally. Read the app signing fingerprint in the Play Console under Release > Setup > App Integrity.

# Play Console > Release > Setup > App Integrity: read the app signing key certificate SHA-1 and SHA-256

2Fix

Copy the SHA-1 and SHA-256 of the app signing key from the Play Console into the Firebase console as extra fingerprints.

# Play Console > Release > Setup > App Integrity > App signing key certificate, then add it in Firebase

3Verify

Install the build from the Play testing track and sign in with a phone number.

# on the device: request the SMS code in the app

Confirmed by developers.google.com

Did this fix it?

Cause 3 of 3

The reCAPTCHA fallback cannot complete

1Check

Without Play Integrity (for example, no Google Play services), Firebase uses reCAPTCHA. That flow needs a SHA-1 on the app and an API key that is unrestricted or allows PROJECT_ID.firebaseapp.com.

# Google Cloud console > APIs & Services > Credentials > your Android API key > restrictions

2Fix

Add the SHA-1 fingerprint, and remove the key restriction or allow the Firebase auth domain.

# Add PROJECT_ID.firebaseapp.com to the key's allowed list, or set the key to unrestricted

3Verify

Try the sign-in again on a device with Google Play services.

flutter run

Confirmed by firebase.google.com

Did this fix it?

How do I stop it coming back?

  • Add SHA-1 and SHA-256 for debug, release and Play App Signing keys as soon as each key exists.
  • Use Firebase test phone numbers (up to 10) while developing, so no real SMS and no real numbers are used.
  • Never ship a build with app verification disabled for testing.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Flutter Android: Failed to load FirebaseOptions from resource

Failed to load FirebaseOptions from resource. Check that you have defined values.xml correctly.

On Android, Firebase reads its settings from a values.xml file that the Google services Gradle plugin builds from google-services.json.

4 causes, each with a fix

Mobile apps

Google Play says the app does not support 16 KB memory pages

check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a

Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.