-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Auth]: credential
property is not set for 'emailAlreadyInUse' errors
#13671
Labels
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
I started investigating and the issue seems to go beyond the SDK and I don't see what the other platforms are doing differently. The backend doesn't return anything beyond that there is an
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I've raised an equivalent issue against Flutterfire at firebase/flutterfire#13268, where most of the detail can be found.
The gist of the issue is that the docs for Flutter suggest that we should be able to retrieve a
credential
property from the exception when an email is already in use (see https://pub.dev/documentation/firebase_auth/latest/firebase_auth/User/linkWithProvider.html). This is true for web and Android, but not for iOS. As far as I can tell, this means we don't have a way of recovering from this error for a user on iOS without asking them to sign in again.I expect the relevant piece of code for the iOS SDK is at:
firebase-ios-sdk/FirebaseAuth/Sources/Swift/Utilities/AuthErrorUtils.swift
Line 290 in 936ddf4
Reproducing the issue
I don't have means to reproduce this exclusively for the iOS SDK, but reproduction steps for the Flutter SDK can be found at firebase/flutterfire#13268.
Firebase SDK Version
11.0.0
Xcode Version
15.4
Installation Method
CocoaPods
Firebase Product(s)
Authentication, Crashlytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetThe text was updated successfully, but these errors were encountered: