Posts

Post not yet marked as solved
0 Replies
732 Views
Our application is written in Swift and uses WKWebView in certain points during the user journey to display our company's web content. The web content, which requires an authenticated user, loads a request with a bearer token and leave the WebView to handle the rest of the page requests and interaction. These request obviously write cookies (both session and non-session). As soon as customer is done with the contents of the WebView, they can tap on the back button of the navigation controller (in which WebViewController is pushed), and navigate to the native views. We are not caching the WebView, so any navigation from the customer to display web content creates a new WebViewController and a WKWebView. Our production application has been tested and currently in store, working without any problems. However, we are seeing a new behaviour in iOS14.5 beta in terms of how session cookies stay across multiple WKWebView intialisation compared to iOS14.4 and before. It seems like despite the deallocation of the WKWebView, sessions cookies live across multiple WKWebView sessions. At least, this is what we are observing. We couldn't find any documentation on this behavioural change. Would anyone be able to direct us to a documentation or explain what might be going on?
Posted
by my-unit.
Last updated
.
Post not yet marked as solved
2 Replies
1.3k Views
Hi,It seems like Apple Script doesn't support accessing Groups which are in the new Reminders. Does anyone know when support will be added or any way around it to get access to Lists within Groups? Similarly, EventKit doesn't see them either.
Posted
by my-unit.
Last updated
.