-
-
Notifications
You must be signed in to change notification settings - Fork 588
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
App Crash when using ASWebAuthenticationSession in iOS 14.5 #664
Comments
you could show code with link
first yes I see some edit about that recently, maybe it depend on swift version |
@phimage Yes forecast must be forbidden, But we required to send like this |
your value of because you pass it , so you could encode it if very necessary (or not is based to ASWebAuthenticationSession is different) |
@phimage yes this is the problem, can you please help me to resolve this ? |
@RahulTak are you passing a full URL as the callbackScheme? Your scheme should not contain a colon. ASWebAuthenticationSession used to only log an error if you passed a full URL as the scheme but as of 14.5 it crashes |
@phimage I am passing the URL like |
that's not a scheme. an url is |
But |
Yep, it worked for us too in 14.4, but check your logs for the error. What changed in 14.5 is that Apple is now crashing instead of just logging an error. |
Description:
File:
ASWebAuthenticationURLHandler.swift
My app is crash when I am using the
Then Crash detail is
if I replace
callbackUrlScheme
withcallbackUrlScheme .addingPercentEncoding(withAllowedCharacters: .urlHostAllowed)
it's working fine.So please let me know how to add this lines into your package and use into my project.
Or should I have to create the new branch for this is send you the PR for merge into this?
OAuth Provider? (Twitter, Github, ..):
OAuth Version:
OS (Please fill the version) :
Installation method:
Library version:
Xcode version:
12.5 (Swift 5.0)
11.4 (Swift 5.2)
11.x (Swift 5.1)
10.x (Swift 5.0)
other: (Please fill in the version you are using.)
objective c
The text was updated successfully, but these errors were encountered: