Additional fields for NativeFirebaseError. #4202
Replies: 3 comments
-
@johnkmzhou if you reach in to node_modules and add some print statements around where the error is generated, you can see if the data is actually available. I am not sure it is, there is no mention of it in the native Android doc: https://firebase.google.com/docs/reference/android/com/google/firebase/auth/FirebaseAuthUserCollisionException or iOS https://firebase.google.com/docs/reference/ios/firebaseauth/api/reference/Classes/FIRAuth#-createuserwithemail:password:completion: They specifically mention in iOS:
and
...which is the strategy I have used with success For native to add the information you want means native would have to call fetchProvidersForEmail itself - extra roundtrips on the network etc - is that what you mean? |
Beta Was this translation helpful? Give feedback.
-
Taking a look at the nativeError the fields aren't available. So it would be great for the the native code to provide it. Email from I don't need native to call fetchProvidersForEmail. I can do that from my own code. |
Beta Was this translation helpful? Give feedback.
-
PRs happily accepted 🙏 - we rely on the community to move things like this forward though, in the absence of a PR, likely nothing will happen |
Beta Was this translation helpful? Give feedback.
-
It would be nice for NativeFirebaseError to adhere more closer to firebase.auth.Error by adding email and credential fields:
Beta Was this translation helpful? Give feedback.
All reactions