ASWebAuthenticationSession cookie

This is breaking our app. Is there any way or method throgh which we can capture and store the cookies?

This is breaking our app. Is there any way or method throgh which we can capture and store the cookies?

What are the symptoms of this memory leak? Is this something reported by the Leaks instrument? Or are you using “leak” in some more generic fashion?As the function to be called from C cannot be formed from a closure that captures context, I create a global variableThat’s a weird way to do things. Most C APIs that support callbacks also allow you to pass in a void * pointer for callback-specific data (typically described as an info pointer, a cookie, a refCon, or something else). You can use this to get back to a Swift closure (see this post) or use it to store the object pointer and then have the C calling convention Swift function recover self from that. For an example of the latter, check out my use of CFHostSetClient in the Swift part of CFHostSample. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Damned if you do and damned if you don't. It turns out that WKWebView doesn't fully deallocate itself. About 30 seconds after you try to deallocate it it generates a call to it's cookie something-or-other and generates a strange error. Search for the error Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service or go directly to stackoverflow 44585980

Thanks for your answer. After reading some documentation and implementing an XPC Service sample for my playground project, it seems, that XPC Services are embedded in apps. I havent found any documentation about external XPC Services, that run independently from a parent app. I found somethin about launch deamons: https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/DesigningDaemons.htmlThis seems to be something different. Then I come back to the idea to make a scriptable main app and write a terminal app, that calls the main app with an object. An other approach could be to deploy an optional embedded XPC Service inside the app folder after the main app was downloaded and installed from the store. But I assume, that this would damage the integrity of the main app. I think, we must find a solution with a helper app, that is downloadod outside the store. We wouldn't be the only app in the store, that requires an additional download. Cookie 5 is an examp

@AlexOak a thousand thank yous for posting this solution. It's crazy that this is necessary, but it works. Did you file a bug report with Apple for this? I've spent untold hours trying to figure out why cookies are sometimes set and sometimes not, with different results pretty much every time I ran the app. Just adding the observer fixes the problem completely.

The problem with syncing cookies to WKWebView lies in WKProcessPool. To properly sync cookie, you have to create an instance of WKProcessPool and set it to the WKWebViewConfiguration that is to be used to initialize the WkWebview itself: private lazy var mainWebView: WKWebView = { let webConfiguration = WKWebViewConfiguration() if Enviroment.shared.processPool == nil { Enviroment.shared.processPool = WKProcessPool() } webConfiguration.processPool = Enviroment.shared.processPool! webConfiguration.processPool = WKProcessPool() let webView = WKWebView(frame: .zero, configuration: webConfiguration) webView.navigationDelegate = self return webView }()Setting WKProcessPool is the most important step here. WKWebview makes use of process isolation - which means it runs on a different process than the process of your app. This can sometimes cause conflict and prevent your cookie from being synced properly with the WKWebview. If you don't use the same instance of WKProcessPool each time you c

The problem with syncing cookies to WKWebView lies in WKProcessPool. To properly sync cookie, you have to create an instance of WKProcessPool and set it to the WKWebViewConfiguration that is to be used to initialize the WkWebview itself: private lazy var mainWebView: WKWebView = { let webConfiguration = WKWebViewConfiguration() if Enviroment.shared.processPool == nil { Enviroment.shared.processPool = WKProcessPool() } webConfiguration.processPool = Enviroment.shared.processPool! webConfiguration.processPool = WKProcessPool() let webView = WKWebView(frame: .zero, configuration: webConfiguration) webView.navigationDelegate = self return webView }()Setting WKProcessPool is the most important step here. WKWebview makes use of process isolation - which means it runs on a different process than the process of your app. This can sometimes cause conflict and prevent your cookie from being synced properly with the WKWebview. If you don't use the same instance of WKProcessPool each time you c

Hello!I finally solve this problem successfully,I used the webView navigationResponse: WKNavigationResponse to get cookies and save them to local storage, and every time the application started, I consulted the localstorage to get saved cookies and inject them into httpCookieStore before the first load of the webViewI hope this can help sameone.Att,Khalid Ait Bellahshttps://www.tialtonivel.com.br