ASWebAuthenticationSession cookie

Hi There, We have a web application with URL testA.comthat uses IFrame and src into a different domain URLtestB.com Page B. The Page B Content-Security-Policy uses frame-ancestors to allow Page A to IFrame into Page B. Also Page B is not using Cookies. This setup works on other devices and its browsers like Android, Windows with Chrome, Firefox Edge but does not work on IOS 13 + on any browsers. The only way to have this works on IOS is to switch off the Prevent Cross-Site Tracking option. We found that this stops working coinciding to the WebKit updates https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/ Just wondering is there anything else that we missed to get this working on IOS? thanks, Kiet Tran

Hi all. I am a software developer and while developing one of the products (it is a plugin for outlook & outreach) I encountered such a problem. Safari disables cookies when sending data from a child window to a parent window that is inside an iframe when using window.opener.postMessage. My plugin (React app) works inside iFrame and in order to implement SSO login and not get a block from Azur, I had to create a separate window with SSO login, where the login procedure takes place. After that, the window is closed, and the data required for login, including cookies, is sent to the parent window. The parent window is in an iFrame. For this operation I use window.open - to open a child window and window.opener.postMessage. - to send data from a child window to a parent window. parent const SSOWindowOpen = () => { const left = (screen.width - 465 ) / 2 const top = (screen.height - 650 ) / 4 const SSOWindow = window.open('/app/static/integrations/ssoWindow', 'SSOWindow', 'resizable=yes, w

Hi, I have the below scenario, 1.While accessing Index.html, server inserts a cookie and a JS file (request.js) 2 . request.js file collects some safari properties and posting it to the same web server like below, but during this call my cookie is missing. Can you please help? I want to retain my cookie value for the JS initiated request.

I am currently trying to run my app in release mode on my iOS device and every time the app starts up, it only displays a white screen. In the device logs I see this when the app is first launched: Error loading metadata for com.outlit.app: Error Domain=ASDErrorDomain Code=513 Loading failed for '/private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A' UserInfo={NSDebugDescription=Loading failed for '/private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A', NSUnderlyingError=0x100e11a30 {Error Domain=MIInstallerErrorDomain Code=78 Failed to read iTunesMetadata.plist from /private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A/iTunesMetadata.plist UserInfo={NSLocalizedDescription=Failed to read iTunesMetadata.plist from /private/var/containers/Bundle/Application/6C87729B-A97F-4D3E-BA9F-ADEADF6BD28A/iTunesMetadata.plist, LegacyErrorString=InvalidiTunesMetadataPlist, FunctionName=+[MIStoreMetadata metadataFromPlistAtURL:error:], SourceFileLi

Hello, I'm implement some SSO features and have a question about ASWebAuthenticationSession and Safari can share cookies? In my demo, it can not share cookie, I looking for some way to do it. Thank you very much.

Hello, We release an App Clip back in December 2020, and everything was working just fine for the longest time. However, sometime relatively recently, not exactly sure when it started, the Domain URL Status started showing this “Cannot Reach AASA File” error; and consequently, the App Clip invocation fails now. The API Validation Tool is saying “Error cannot parse app site association file” as the reason. We have not made any changes in the App / App Clip, and the associated domain is still set as appclips:mobileapp.caesars.com The Apple App Site Association file hasn’t been changed either, and the format still matches that specified on https://developer.apple.com/documentation/app_clips/associating_your_app_clip_with_your_website. The AASA file returns no problem in a browser and from curl command as you can see below: Last login: Tue Jul 12 09:11:11 on console curl -v https://mobileapp.caesars.com/.well-known/apple-app-site-association * Trying 192.230.66.155:443... * Connected to mobileapp.caesars.com (192

After a few experiments with HTTPCookieStorage.sharedCookieStorage , it seems that the behavior for the storage in that scenario involves some kind of OS flushing / synchronisation: There seem to be cases when the storage is updated, yet the updates aren't visible. Examples are: update by a process not visible by other processes from the same app group, hard crash / killing, etc. This all led me believe that there is some caching involved (of course, i can only guess, as the documentation provides 0 clues on internals). In some cases, such as authentication session cookies, this could have disastreous consequences (such as login out a user for no reason). => Is there some kind of way to force the flushing on the cookies, for the important ones ? Are there recommended alternatives for storing authentication cookies shared accross apps and extensions (keychain ?)

I finding some for ways for turn off dialog popup when using ASAuthenticationSession. I also set prefersEphemeralWebBrowserSession = true for not display dialog confirm but it also turn off shared cookies between apps. So does Apple support anyway for still shared cookies and doesn't show any dialog confirm. Thank you very much.