Before explaining the problem let me give the specifications. We are using SFSafariViewController and OAuth 2.0 mechanism for authentication. Also we are using Universal Link based Redirect URI.
I have uploaded the AASA file in the particular domain as expected for Universal Link. Also checked that it is getting downloaded when I am installing the app in the device. And our device got MDM profile provided by our organisation. Now coming to the issue:
When I am onboarding with my app, onboarding is successful, if I don't opt for certificate(picked up from the MDM) authentication. But, if I opt for certificate authentication after providing the certificate identity to the idp the callback is not happening. It stays in the SFSafariViewController. The expected behaviour is to resume the NSUserActivity of the app through appdelegate.
Any idea how to resolve this?
Post
Replies
Boosts
Views
Activity
Before explaining the problem let me give the specifications. We are using ASWebAuthenticationSession and OAuth 2.0 mechanism for authentication. Also we are using Universal Link based Redirect URI.
I have uploaded the AASA file in the particular domain as expected for Universal Link. Also checked that it is getting downloaded when I am installing the app in the device. And our device got MDM profile provided by our organisation. Now coming to the issue:
When I am onboarding with my app, onboarding is successful, if I don't opt for certificate(picked up from the MDM) authentication. But, if I opt for certificate authentication after providing the certificate identity to the idp the callback is not happening. It stays in the Safari. The expected behaviour is to resume the NSUserActivity of the app through appdelegate.
Any idea how to resolve this?
Hi All,
I am getting stuck while authenticating using ASWebAuthenticationSession. When I am authenticating using a certificate(provided through the MDM profile) the ASWebAuthenticationSession window is stuck with the following image shown in the window.
It seems that the ASWeb is not redirecting to customSchemeURL so that we can pick up the authorization code from there. Strangely enough, when we cancel the flow and again retrigger the authentication everything works fine. This scenario happens only once for a fresh installation.
Any idea how to resolve the issue?
I was testing my framework APIs. My framework has the following sample code
open class TestManager {
let appendStringHandler: (String, String) -> String
public init(appendHandler: @escaping (String, String) -> String = TestManager.appendStringObject(text1:text2:)) {
self.appendStringHandler = appendHandler
}
public class func appendStringObject(text1: String, text2: String) -> String {
return text1+text2
}
public func printString() {
print(appendStringHandler("test1", "test2"))
}
}
I am creating an object like this
let test = TestManager() in my project which is using the framework.
I am getting the following error while building in Debug mode and in Xcode 14.3
Undefined symbols for architecture x86_64:
"_$s17ReusableComponent11TestManagerC18appendStringObject5text15text2S2S_SStFZ", referenced from:
$s17ReusableComponent11TestManagerC13appendHandlerACS2S_SStc_tcfcfA_S2S_SStcfu in ViewController.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
After some investigation found out that changing the debug Compilation Mode to "Incremental" is fixing the issue.
Observations:
Xcode 14.2: There is no issue when Compilation Mode is "Whole Module" in Debug/Release both
Xcode 14.3: Having issue when Compilation Mode is "Whole Module" in Debug. Release Mode doesn't have any issue with "Whole Module" mode.
I was wondering what changed in xcode 14.3? Please let us know how can I stick with the "Whole Module" compilation mode without the error.
I can see that some UITextViewDelegate methods are deprecated. Any Idea for the alternative of the following delegate method? Will there be a new alternative method in the future?
optional func textView(
_ textView: UITextView,
shouldInteractWith URL: URL,
in characterRange: NSRange,
interaction: UITextItemInteraction
) -> Bool
I was testing bytes(from:delegate:) API from URLSession. I was testing the implementation of the delegate. I didn't get any callback to the delegate when I got 400 status code in the response(No token is provided). I have implemented other delegates also. Still I didn't get any callback in any of those functions. Please let me know if I am missing something here?
I was loading a URL using SFSafariViewController in my app and also implemented the SFSafariViewControllerDelegate. I noticed that when I am running my app on iOS, I am not getting the callBack in safariViewControllerDidFinish(_:) until or unless "Done" button is pressed. But when I am running it on MacCatalyst following behaviour is noticed:
default browser is launched.
I get a callback in safariViewControllerDidFinish(_:) without any of my action(like pressing "Done" button).
Is this the expected behaviour? I am curious to know why I am getting callback in safariViewControllerDidFinish(_:).