Cookies not working on iOS 13.3 beta

[kas84]

Hi, since iOS 13.3 beta I am having issues with cookies not setting correctly on a cordova app.

I am using the latest version of ionic-webview:
cordova-plugin-ionic-webview 4.1.3 "cordova-plugin-ionic-webview"
I attach login response with set-cookie headers

And then check user get http without any cookie set.

Anybody else experience this bug?

[NiklasMerz]

This is most likely a Webkit bug

[kas84]

Yes, seems like it, thanks! In case they don't fix it... is there a way to change http calls to go from a webkit http request to a native http request? I've checked https://ionicframework.com/docs/native/http, is there an easy way to integrate this into ionic v1 angularjs $http requests?

By the way, this also happens on iOS simulators since 12.0+

[NiklasMerz]

You might try #448 . I built this for cookie issues in the initial iOS 13 release. It works quite well if you can adjust all your URL to use the custom scheme.

[kas84]

What does that mean? I am using local http to serve the ionic app. Would I need to move to custom scheme like ionic://** ?

[NiklasMerz]

If you use the code from #448 via https://github.com/NiklasMerz/cordova-plugin-ionic-webview#schemehandler you can use the Javascript method window.Ionic.WebView.convertFileSrc() to convert your URLs.

Your HTTPS URL like https://example.com become /_https_proxy_example.com. This means your code will go through native methods of this plugin and you cookies will be set to the webview and all other requests.

[kas84]

Oh, I see. So basically when using a get like $http.get("https://google.com"), I should do $http.get(window.Ionic.WebView.convertFileSrc("https://google.com")) and then it would go through the native layers?

[NiklasMerz]

Oh, I see. So basically when using a get like $http.get("https://google.com"), I should do $http.get(window.Ionic.WebView.convertFileSrc("https://google.com")) and then it would go through the native layers?

Yes correct. Thats the idea of this PR. We call this 'proxy' because the HTTP requests are not done by Webkit but native URLSessions instead. This handles cookies correctly in the cookie store and syncs them to the webview.

[kas84]

Awesome! I'll check it out! Thanks!

PS: It works!! Now I have a backup plan!

Many thanks @NiklasMerz

[kas84]

On 13.3 beta 3 this bug is NOT fixed. I am not familiar with how Apple deploys versions, is there going to be a Golden Master before 13.3 goes mainstream?

That is, so we know for sure that they’re going to break this and need to go http native or not.

_{Sent with GitHawk}

[NiklasMerz]

We will see if it gets merged in for 13.3 GA. Always a suprise unfortunately.

But it did work at some point in 13.2 so I have hopes they will fix this regression.

[kas84]

I have the way around prepared with an if, but if I have to go http native and break sessions, I’d rather stay on http native even after they fix it.

Because I don’t want to break sessions twice

_{Sent with GitHawk}

[kas84]

Fixed by Apple on 13.3 beta 4

[Lucaszw]

This is working for me on a physical iPhone, but the cookie problem seems to be persisting with the iOS simulator. Is anyone else still encountering this?