Firebase Auth Sign-in does not work after releasing flutter project to Play Store

2,112

Solution 1

It wasn't an SHA-1 issue. It had something to do with shrinking code during build. See https://stackoverflow.com/a/65511857/14834849

Solution 2

When the application is uploaded to Google Play, a new SHA1 code is generated

All you have to do is copy the new code and add it to the Firebase project.

when you signed your APK with SHA-1 and upload the APK it only signed by you but as per the new update it is also signed by Google Play for more security.

You can check this.

Share:
2,112
nickinspace
Author by

nickinspace

Updated on December 26, 2022

Comments

  • nickinspace
    nickinspace over 1 year

    I'm running into trouble signing into my Android app after I released it to the Play Store (internal and closed testing releases). Basically, my sign-in options (email & third party) do not work. Firebase is connected, because I can properly create accounts and write to Firestore via the app. If I have an error (wrong password, wrong email, etc), Firebase will kick that error back to me. However, a “successful” login simply does not result in a finished sign in process, and my app is stuck on that await method forever.

    I have no problems when running on an emulator, running on Android devices straight from Flutter (both release and debug modes), or running on iOS in any capacity.

    What is going on here? I don't think it's my actual code, and I must be missing a step as part of the Android release process. I have permissions requested for internet and access network state, the SHA keys should all be good to go for Firebase (added debug, release, and Play Store keys) and my firebase dependencies are the most up to date.

  • nickinspace
    nickinspace over 3 years
    I have done this. I have 3 SHA-1 keys in Firebase associated with my Android app. 1 is my original debug key, 1 is the release key from the keystone on my computer, and 1 is that key from Google Play. A new google-services json was generated and added to my project, but the same issue exists.
  • Gene Bo
    Gene Bo over 2 years
    This fixed the issue after being stuck for several days, big thanks. App SHA-1 in Play Console is under: Release > Setup > App integrity