ASWebAuthenticationSession cookie

Hello,We have tried JRWan method and it worked. We wonder if there is any official documentation that confirms that all Safari Cookies can be readed using Cookies group container identifier in OS X.Can any apple developer confirm this or another user share a link ?Thanks in advance,Nicolas

I understand that as of iOS9 you should be able to read cookies with SFSafariViewController.If I set a cookie on my page in JS using the following:var dd = new Date(Date.now() + 1000 * 60 * 60 * 24).toGMTString();var expires = expires=+ dd;document.cookie = mycookie=cookievalue; + expires + domain=.mydomain.co.uk ; path=/ ;If I do :- (void)safariViewController:(SFSafariViewController *)controller didCompleteInitialLoad:(BOOL)didLoadSuccessfully{ NSHTTPCookieStorage *storage = [NSHTTPCookieStorage sharedHTTPCookieStorage]; NSArray *cookiesArray = [storage cookies];}cookiesArray is always empty.If I use a traditional UIWebView-(void)webViewDidFinishLoad:(UIWebView *)webView{ NSHTTPCookieStorage *storage = [NSHTTPCookieStorage sharedHTTPCookieStorage]; NSArray *cookiesArray = [storage cookies];}I get the cookie I was expecting.Any ideas what I might be doing wrong?

Thank you for pointing this out! I have found the same issue in my app, and couldn't for the life of me figure out why cookies werent being saved anymore. Awaiting response on why this changed, but will patch for now.

Got it to work two days ago by erasing all cookies and disabling safari suggestions.But today I get too many redirects again, on every one of my devices.Nothing helps.

It worked briefly for me at the end of last week as well, even though I had not cleared any caches or cookies. Today, no go. It worked on Chrome though, so I used that to file a bug report on the bug reporter.

I can help you set up a notification handler but I must reiterate that using undocumented notification strings is a good way to:Get rejected by App Review, perhaps now, perhaps in the futureHave your app break after some OS updateYou really don’t want to do this.I get the error: A C function pointer cannot be formed from a closure that captures contextBy default Swift functions (including methods) use Swift calling conventions. This allows them to do clever things like capture values from the surrounding context. For example:func startTimer(with message: String) { Timer.scheduledTimer(withTimeInterval: 1.0, repeats: false) { _ in print(message) } }Here we’re passing an anonymous function (a closure) to scheduledTimer(withTimeInterval:repeats:block:). Note how that function ‘captures’ the message value from the surrounding context, so it can print that message when it runs after the timer fires. In C, functions do not support this. C functions can only access:Their parametersGlobal variablesSwift has the abili

I've got rid of this. Neither clearing cookies nor using other browser helped.Once I opened other certs page (https://developer.apple.com/account/mac/certificate/), iOS cert page shows my certs correctly again.I have several certs & profiles for iOS but no ones for OS X, if it helps.

Are HTTPCookies stored encrypted by HTTPCookieStorageStorage?No. However, I believe the cookie store is covered by file protection.In the case of an authentiction cookie, if the cookie is not stored encrypted, it could be removed from the cookie storage and stored in the keychain. Of course it would need to be set and removed before and after sessions.I’m not sure if this is a suggestion for Apple or a plan of action on your part. If it’s the former, feel free to file an enhancement request for that, although keep in mind that there’s no obvious way to identify security-critical cookies.Please post your bug number, just for the record.If it’s your plan of action, my only comment is that, if you know tha a specific cookie is critical to security, you might be better off manually managing that cookie rather than relying on the cookie store. That way you can make security guarantees, rather than relying on how the cookie store happens to be

It's possible as it clears the cookies

Clear Safari cache & cookies.

It is not uncommon for the backend to be unreliable, but when they take the time to convey that message, it tends to be more of a full stop than just another blip.The 'status' page tends to be eye-candy...operational theater that works to project an impression more than hard info, it seems.Best anyone can do when these outages surface is to keep trying, clear Safari cache/cookies and be patient.