ASWebAuthenticationSession cookie

Hi,We are using WKWebview to load mobile webpages in our app. While loading a particular mobile webpage, the response sets certain cookies.Later we need to call a rest api using the stored cookies. So, we call the below method to get all the cookies. But what we notice is some cookies that was suppose to be set after we got response goes missing. The behaviour is quite intermittent. Sometimes those cookies are seen. And sometimes not.[self.webView.configuration.websiteDataStore.httpCookieStore getAllCookies:^(NSArray<NSHTTPCookie *> * cookies) { NSLog(@cookies before:%@, cookies); }];What could be the possible reason for this kind of behaviour.

Hello,We are making custom QR codes that when used with the iPhone camera bring up a c# web page in Safari. This web page makes and saves a persistant cookie that is good for one year, and it seems to save it cookies correctly for my domain.If we take a pick pictire of the QR code and bring up the web page a second time, its does not see ths Cookie, almost like it walls it off for each Safari invocation.When we do this with the Mac based Safari, even if we quit all the Safari instances, the Cookie remains. This seems to demonstrate that our Cookie saving + one year logic seems to be working on the desktop.It's only the the iOS based Safari that is causing us trouble.Could someone point us in the right direction ?Thanks

Hi,We are upgrading to WkWebview and facing some challenges. We have Angular js file locally and trying to load on wkwebview. Below are the steps,1. We call our server for Auth token before load.2. Add the cookies in headers.3. Add userScripts.4. We are handling js callbacks through WKScriptMessageHandler, works perfect.5. We are sending our domain back to js through Prompt, works perfect.6. And in Angular js they are calling the server where it is always going to failure block. It works in UIWebview, but fails in wkwebview.We found in some stackoverflow that it is issue with CORS and our server team did add the configuration. Still we are seeing 401 and 405 error in charles proxy when the call goes from WKWebview. We cannot downgrade to UIWebview since it will be removed from Apple, can someone please help.

Hello, I am try to use WKWebview to handle webpage load. But I have met an authorisation cycle.Our website have more than one redirect(302).Just like PageA-&gt;PageB-PageC-&gt;PageA. The PageC need cookies of PageB'response.The cookies of PageB'response seems like right,I can see the right cookies of response. When PageB redirect to PageC the PageC's request header have no the cookie before.I want to inject cookie, But The delegate of WKWebView can not handle 302 response, So I can not inject cookie in right way?

The industry is evolving to enhance privacy and block trackers, and it's well covered in WebKit's website post: https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/However nothing is mentioned about WKWebView, I would like to understand the direction this will take for it, specific questions are:- Will it (ever) apply to WKWebView?- Would there be options to turn it on/off?Thanks!

The script is written in PHP. At the first (there is no information from the site in the browser yet) document request, the server sends a cookieif(isset($_COOKIE['PHPSESSID'])) session_id($_COOKIE['PHPSESSID']); session_start();then the whole documentexit($variable);There are elements in the document (for example img) upon request of which these COOKIES should be sent, but they are not sent. If the element is reloaded for example via js, then everything will go. The problem is with Apple in the first connection (dock request).

I succeed to make Apple Signin working in my company SSO developed on a spring boot stack.Main problems:No icon customization. It must be linked to a deployed native application.Apple Signin Callback is a post method. We have a cookie with samesite=lax. So the session is lost. We don't remember the state value or the redirecturi. My workaround was to create another cookie withe samesite=none and a short TTL, only for the apple-signin.Spring Oauth server doesn't support post method callbackSpring social does not support id_token.I have forked the spring social project to adapt. So the maintenance will be more complex and will take more times to follow spring social updates,I guess many sites will let samesite=none and the security will be globaly bad for the end user (the best is the enemy of the good).