Closed artsiom-dorakhau closed 6 years ago
Excellent, thanks for sharing this info and the PR! 👍
Welcome! I hope somebody will find this useful.
Doh! Wish I would've seen this before. Doesn't this also mean that section 6 of the readme describing how to read Safari data and cookies and pass that data to the app is no longer valid? I've spent the last hour or so trying to do just that with no success. I'm hoping against hope that I'm just missing something on my end and we can still do that somehow...
Since iOS 11 Safari and other apps get their own cookies and website data.
This means that cookies, local storage, and other browsing data will be contained within your app and scoped to your app. And this means that the user won't automatically be logged in to whatever accounts they were logged into in Safari. What this does is it will prevent cross-app tracking of user's browsing activity that you and your users may not have even been aware about. And ultimately, it helps keep users' browsing activity private and scoped within your app.
https://developer.apple.com/videos/play/wwdc2017/225
So the following point of "Advantages over InAppBrowser" section is not valid anymore: "Since this is the system's main browser, assets like cookies are shared with your app, so the user is still logged on in his favorite websites."