ASWebAuthenticationSession cookie

I have an app that uses the Slack API, and I’m trying to use ASWebAuthenticationSession on watchOS 6.2 to allow for login on watchOS. I was able to display the login form and enter my username and password, then I saw this displayed:Unable to set cookie You need to enable cookies to sign in.Is this something Slack needs to account for, or is there a way for my ASWebAuthenticationSession on watchOS to enable cookies?

Google are starting to enforce stricter cookie handling in Chrome 80 next week. In researching this change it appears iOS 12 and below and macOS 10.14 and below have a core networking issue that prevents proper handling of the Samesite=none cookie attribute.It's reported that older versions of CFNetwork/Safari/Webkit erroneously handle Samesite=none as the equivalent of Samesite=strict. This might have big consequences as web service providers start using the Samesite attribute more widely.There are details in the Webkit bug 198181 (now resolved) thread here: https://bugs.webkit.org/show_bug.cgi?id=198181Part way down is a reference to a CFNetwork/NSHTTPCookie fix for this issue under rdar://problem/42290578.However, other comments indicate that this fix is unlikely to be back ported to previous macOS & iOS versions.Does anyone have a definitive answer as to whether iOS 11/12 and macOS 10.13/10.14 will recieve a fix for the cookie Samesite handling issue?

We have an application that has an Iframe inside the main page. When the application launches it access the abc.com domain and creates a cookie name with abc_cookie. Then the browser address bar changed and redirects to the pqr.com and loads an iframe inside the main page. When the iframe src was set to abc.com, above abc_cookie was not sent with an HTTP request. But it was sent with safari 12. I added `SameSite=None` for the cookie but no success. How can I make this work in Safari 13 as well?

Is it possible to change/customise the look of ASWebAuthenticationSession to remove or disable the Refresh icon?

Suddenly Safari in my macOs High Sierra is not able to browse https://appstoreconnect.apple.com/loginIt just keep on loading. However, I can browse it with Chrome. I have tried clear Safari cache and cookie but it's still the same.Here's the screenshot of Safari and Chrome running the same address at the same time in my mac.https://i.ibb.co/GdH7jXV/Safari.jpgHow can I fix this problem?

I have an app where we create a UAT build and PROD enterprise build internally. We have apple-app-site-association on two different servers. One for UAT and one for PROD. Apple Site Validator says both are good. Both apple-app-site-association are at the app root (not .well-known).On IOS 11.2.1, both UAT and PROD build work fine. Universal links work perfectly.On IOS 13.1 (or any 13+) UAT works. PROD does not work. This is the confusing part because both are using the same TEAM, profile and cert. Only difference is bundleID. Both bundleID's are all lowercase, except the team name. Both are all UPPERCASE. I verified what is in the app bundle as ID and what is in the apple-app-site-association file. Identical.Only difference I see is in the response from the server. PROD one returns cookie as part of response. This doesn't seem to bother ios 11 or 12. It might not bother ios 13. But just an observation.UAT Response Header : apple-app-site-associationHTTP/1.1 200 OKX-Backside-Transport: OK OK,FAIL FAILC

I cannot add New App in the App Store Connect.When I try to add it shows me error with message You have no eligible Bundle IDs for iOS apps. and offers to create new one.BUT I already have 2 not used yet App IDs. Moreover, I've tried to create one new, but it have no affect.I've read info I was able to find with the Goodle Search, but haven't found there anything works. // By the way, I confirmed all terms in corresponding App Store Connect's section; removed some not actual Apps from My Apps section; reloged in the account with Safari browser with clearing all history / cookies / caches; etc but nothing solve the problem.What to do with it? I've wrote to the apple support and them advised me to also create thread here too.Screenshot:https://i.ibb.co/Wkf4QrH/Screen-Shot-2020-03-02-at-4-11-29-PM.png

Hi,I used the browser (Safari / Edge / Chrome) on my iPhone to access my application and found that I cannot access the js resource file normally.The code snippet looks like this: <script type = 'module' src = 'main.js'>After my research, I found when requesting JS resources, since type = 'module', it became a cross-domain request. Due to cross-domain, the required cookies are missing when requesting main.js on Browser, which causes the page to not display properly.This is the test result I did on iOS 13.31 and Mac OS 10.15.3. Y means resources can be loaded normally, N means resources cannot be loaded normally. iOS 13.31Mac OS 10.15.3Edge N YChrome N YSafari N NMy question: Is this related to the browser kernel?If it is related to the kernel, is this a feature or a bug?How should we solve the problem that main.js does not load properly in these browsers?Thanks.

Our company is rolling out the 'Sign in with Apple' feature, when deployed to our alpha env, we met a block issue: when Apple redirect back to our service, sometimes it will miss all cookies, which one is used to mark which server the original request from, Our alpha env have more than one server.There's some probability that this behavior will happen. Any of you have this situation?