Issue
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.
Solution
It wasn't an SHA-1 issue. It had something to do with shrinking code during build. See https://stackoverflow.com/a/65511857/14834849
Answered By - nickinspace
Answer Checked By - Robin (JavaFixing Admin)
