-
Notifications
You must be signed in to change notification settings - Fork 193
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
Failed execution for Auth.socialWebUISignInAPI with error: AuthError: Make sure that the amplify configuration passed to Auth plugin is valid #3861
Comments
Hi @ChurikiTenna,
The key ID is created by Apple during the "Setup Your Auth Provider" step as found here which is the step before you call `amplify update auth`` Thanks for your detailed reproduction steps. Just wanted to clarify something since it wasn't explicitly called out, between steps 4 and 5 in your provided steps, did you provide Apple with the hosted UI endpoint URL that was generated in step 4? It's the last section in the Configure Auth Category section right before the Update Info.plist step. |
Hi @vincetran ! Thank you for your response. The key seems to be created after |
@harsh62
Please correct me if I am wrong. |
Ahh .. May be I confused you a little. Let me clarify a few things..
|
Describe the bug
It is not a bug, I think I am doing something wrong.
I followed this steps to Sign in with Apple, but get this error:
I have checked all the values are correct at least 3 times. What else do I need to check?
One concern,
amplify update auth
require key id before creating the actual key. how is it possible to get a Key id before creating them?Steps To Reproduce
Expected behavior
Be able to Sign in with Apple
Amplify Framework Version
2.39.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
latest
CLI version
12.12.6
Xcode version
Xcode 15.4 Build version 15F31d
Relevant log output
Is this a regression?
Yes
Regression additional context
No response
Platforms
iOS
OS Version
iOS 17
Device
iPhone 11 & 15
Specific to simulators
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: