Question 128363 in Android Studio Question posted in
The official documentation can be found here.

Android Studio – Why signed release APK does not allow user to sign in but built debug apk does?

I had an app on Google Play that went live but when the 1st customer who installed it couldn’t sign into the app, I was advised by another developer to generate a signed APK (filename: app-release.apk) and then drag it onto my emulator for testing. I did this and I got an error when trying to sign in, so I unpublished the app until I fix this.

I then tried by building an APK which gave me a file: app-debug.apk. I dragged this onto my emulator and was able to sign in with no issues.

What might I be doing wrong?

When I run the app from Android Studio onto the emulator, it runs fine, and signs me into my Firebase Database authenticated accounts.

Tags:

2

Answers


  1. 0

    You might have enabled obfuscation (R8) for release builds and not written the required -keep rules for it. Without a stack-trace this is quite a theoretical question, but likely it would show a ClassNotFoundException, because the name of some class or class member had been obfuscated, which shouldn’t have been obfuscated.

    Login or Signup to reply.
  2. 0

    Your project may be using specifying different servers for debug and release builds. This is a common practice when you don’t want to corrupt the release database with debug/testing data. See this SO post for an example. I’d check your build gradle and see if I could spot something like this there.

    So, the release server may be down, whereas the debug server may still be up and running.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search