You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Widcket, guys,
unfortunately, Auth0 forum could not help me with explanation of SFSafariViewController usage in SwiftUI and suggested I ask here for the answer.
There is one totally clear thing in the FAQ:
Auth0
.webAuth()
.provider(WebAuthentication.safariProvider()) // Use SFSafariViewController
.start { result in
// ...
}
and one unclear:
SomeView()
.onOpenURL { url in
WebAuthentication.resume(with: url)
}
Would you please provide a little bit more information or a code example?
I couldn't figure out where in my code to do resume() und what URL should I pass on? Allowed callback URL from the application page? An example would be great!
Thanks in advance.
Describe the ideal solution
Explanation or code example.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Ok, resolved.
Custom URL scheme must be configured.
"In Xcode, go to the Info tab of your app target settings. In the URL Types section, click the + button to add a new entry. There, enter auth0 into the Identifier field and $(PRODUCT_BUNDLE_IDENTIFIER) into the URL Schemes field."
Checklist
Describe the problem you'd like to have solved
Hi, Widcket, guys,
unfortunately, Auth0 forum could not help me with explanation of SFSafariViewController usage in SwiftUI and suggested I ask here for the answer.
There is one totally clear thing in the FAQ:
and one unclear:
Would you please provide a little bit more information or a code example?
I couldn't figure out where in my code to do resume() und what URL should I pass on? Allowed callback URL from the application page? An example would be great!
Thanks in advance.
Describe the ideal solution
Explanation or code example.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: