firebase-admin-node: development_mode_mismatch when we try to patch whitelisted phone number
Environment
- Operating System version: Ubuntu 14
- Firebase library:
firebase-admin-node - Library version:
6.3.0 - Firebase Product: auth
Problem
Steps to reproduce:
When we patch whitelisted phone number by passing same phone number as one of argument, it corrupts the auth record and doesn’t allow us to login later. Is this intended behavior? We shouldn’t be sending phoneNumber as one of argument to update call for whitelisted numbers? It works fine for regular numbers.
- Whitelist a phone number from phone auth provider.
- Login with whitelisted number and logout.
- Patch whitelisted number using
updateUsermethod by passing same number as one ofUpdateRequestproperty (phoneNumber). - Try to sign in with whitelisted number again. Sign in fails with following error.
DEVELOPMENT_MODE_MISMATCH.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (5 by maintainers)
Facing the same issue: PlatformException (PlatformException(FirebaseException, An internal error has occurred. [ DEVELOPMENT_MODE_MISMATCH:Non-development mode Verification Proof given in development mode request.
Facing the same issue:
com.google.firebase.FirebaseException: An internal error has occurred. [ DEVELOPMENT_MODE_MISMATCH:Non-development mode Verification Proof given in development mode request. ]while using test account. No problem while using real number.We’re experiencing the same problem, so we cant use test account. We have to use real phone number to debug. Any news?
I see. So you are saying that
updateUserworks with the test phone number on same user but sign in will fail after that. Seems like a bug. I will notify the right channels about this.The fix should be in prod at this point. You should not be getting the
development_mode_mismatcherror anymore.Workaround is not to patch whitelisted phone with
phoneNumberas one of argument.