Cookies problem in iOS beta 18

Question

Created Aug ’24

Replies 5

Boosts 2

Participants 5

I have a hybrid mobile app which loads web server screens in its iframe(which is under the WKWebView); an https request is initiated from the mobile app to the web server which returns the html page to be loaded in the iframe. The calls which are initiated from outside the iframe have cookies maintained in their requests, while the ones initiated from inside the iframe(web server page) loose the cookies and do not inherit them in IOS beta 18 while It worked fine in the previous IOS versions. Anybody has infos about this or similar cases?

Boost

Answer 1

toasty01 OP

Sep ’24

hi. We have the exact same issue. We noticed this with the actual ios18 release.

Does anyone have a hint how to fix this?

0

Answer 2

jkhkhbjhbj OP

Oct ’24

Any update or fix found for this issue ?

0

Answer 3

jkhkhbjhbj OP

Oct ’24

tried with iOS 18.1 beta version. But seeing failures of my WebView to load. Any update or fix found for this issue ?

0

Answer 4

Rikardt OP

Oct ’24

@jkhkhbjhbj In the Cordova context we got the Cookies to move in both IOS 18.0 and IOS 18.1. IOS 18.0 being more complex. We basically had to manually inject the cookies from the NS to the WK store. This worked in 18.1 but in 18.0 we have had to one more step to launch the InAppBrowser plugin with a dummy URL to the server (Hidden Call). This then made the cookies available in the IFrame as well.

!Important : You could also be hitting issues with the Cookie SameSite where when not passed from server will default to Lax not None like it did before. This can cause issues in an iframe as well as it does not send Lax on post requests. We fixed this by making sure None was set from the server side ( can't do this locally).

0

Answer 5

t1-sdaoust OP

4w

As @Rikardt pointed out, this could be an issue with Apple changing the default cookie SameSite. I created another post about it here with a sample app: https://developer.apple.com/forums/thread/765199 Hoping Apple will have a workaround, as I cannot change what the server does (Salesforce in my case).

0