-
Notifications
You must be signed in to change notification settings - Fork 48
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
documentation incorrect : Native SFSafariViewController iOS/MacOS #89
Comments
Sorry for the delayed response, I cannot duplicate this issue. I am using it in my own projects. If it crashes, check the console for the crash. Make sure you have added the CFBundleURlTypes to the info.plist: SimpleAuth.NativeSafariAuthenticator.Activate (); |
Thanks for response will try asap
Sent from Outlook<http://aka.ms/weboutlook>
…________________________________
From: James Clancey <notifications@github.com>
Sent: Tuesday, March 19, 2019 5:26 PM
To: Clancey/SimpleAuth
Cc: Fun stuff; Author
Subject: Re: [Clancey/SimpleAuth] documentation incorrect : Native SFSafariViewController iOS/MacOS (#89)
Sorry for the delayed response, I cannot duplicate this issue. I am using it in my own projects. If it crashes, check the console for the crash. Make sure you have added the CFBundleURlTypes to the info.plist: SimpleAuth.NativeSafariAuthenticator.Activate ();
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#89 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AM1cLHhwzNF3_vp4p0ZYFcBQ8JDPt7NKks5vYJE5gaJpZM4bAfNk>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You indicate Native SFSafariViewController iOS/MacOS in documentation.
The line of code below doesn't work on Xamarin.mac
Then call the following line in your iOS AppDelegate FinishedLaunching method;
SimpleAuth.NativeSafariAuthenticator.Activate ();
app just hangs on Xamarin.mac when trying to authenticate I line above used.
please assist
The text was updated successfully, but these errors were encountered: