Post

Replies

Boosts

Views

Activity

Not able to start authentication by using ASWebAuthenticationSession in Big Sur Beta 9
This seems to be a regression and it works fine in early beta versions. When start a ASWebAuthenticationSession by setting prefersEphemeralWebBrowserSession to false (default), there will be a popover asking "AppName" want to use "certainurl.com" to sign in. When tapping the continue button from popover, a safari window will show and user can put username and password to continue authentication. However in beta 9, when user clicks the continue button, the popover will dismiss and send error back into the completion block which was passed in when init the ASWebAuthenticationSession. The error code is ASWebAuthenticationSessionErrorCodeCanceledLogin, which should only happen when user clicks cancel instead of continue button. Here is a public project if you want to give a try: https://github.com/Azure-Samples/ms-identity-macOS-swift-objc
5
0
2.2k
Oct ’20
completionHandler is not triggered when using ASWebAuthenticationSession on iOS 14 iPad
When using ASWebAuthenticationSession to show a login session on iPad on iOS 14, the user can tap the background to dismiss the login session, however the completionHandler is not triggered and there is no way to tell when the user canceled the Auth session. I am using the following code from Apple to reproduce the issue on iPad: https://developer.apple.com/documentation/authenticationservices/authenticating_a_user_through_a_web_service?language=objc
1
1
1k
Oct ’20
callerBundleIdentifier in ASAuthorizationProviderExtensionAuthorizationRequest is different from actual App bundleId
I have an App with bundleId in Xcode as "com.companyname.abc.123" when using ASAuthorizationProviderExtensionAuthorizationRequest with Enterprise Sso plugin feature, the callerBundleIdentifier shows a different (com.companyname.abc without 123 in the end) which failed our validation. Do we know where the callerBundleIdentifier comes from? I noticed something called audittoken as well from console logs, but no idea how it is generated.
1
0
1k
Jul ’22
Mac: Best way to distinguish native app process and script process spawned from executable (e.g. python node) through process_id
I'm working on a Mac app that receives a process ID via NSXPCConnection, and I'm trying to figure out the best way to determine whether that process is a native macOS app like Safari—with bundles and all—or just a script launched by something like Node or Python. The executable is signed with a Team ID using codesign. I was thinking about getting the executable's path as one way to handle it, but I’m wondering if there’s a more reliable method than relying on the folder structure.
1
0
137
1d