ASWebAuthenticationSession cookie

I've been having real trouble using a third party to manage cryptographic signing of content with my web app. This works perfectly when the webapp is added to Homescreen and the webmanifest is set todisplay: browserHowever, as soon as the app is set todisplay: fullscreenfunctionality is broken as it behaves as if it is a standalone app, preventing access to the service provider's iframe within my app. Essentially it exhibits behaviour as if `Prevent Cross-Site Tracking` is on, even though I have this switched off in Safari's Settings.The solution might be to allow a setting `Prevent Cross-Site Tracking For WebApplications` to be switched off.Essentially I need to be able to allow Cross Site LocalStorage so that when I load the iframe to www.somesite.com, it is allowed to access localStorage for www.somesite.com within the PWA.I would like everything else to stay the same, essentially just allowing a fullscreen experience of the safari page.

3rd party cookie does not work in iOS 13.3 beta.it's unable to write 3rd party cookie in iframe.Safari setting Block All Cookies AND Prevent Cross-site tracking are turned off.it works in iOS 13.2.2 (official release).

I have to play HLS stream and it is secured/protected. In order to download manifest file and further ts file it is expected that request have valid Cookies information sent. I do receive Cookies information from server but it is not part of response header whereas it comes as part response String. It means Cookies automatically does not become part of NSHTTPStorage and application have to consume response string and fetch Cookies information from there; further need to be set while initialising AVURLAsset. As per AVURLAsst documentation in order to send Cookie information we should use options AVURLAssetHTTPCookiesKey. I have mentioned in below code how to initialise AVURLAsset using this keylet cookieOptions = [AVURLAssetHTTPCookiesKey: Any] let assets = AVURLAsset(url: url as URL, options: cookieArrayOptions)Main problem is how to set value against AVURLAssetHTTPCookiesKey. It take value of 'Any' type.Since Apple just mention it expect Any value and does not tel

I've implemented a VPN app with Packet Tunnel Provider for iOS and macOS.During the conenction process, in addition to the username and the password, I'm also sending a cookie to my server.Now I have this scenario: The user configured the VPN to be on-demand with a rule to always connect, and then he connected the VPN.While the user is connected, some time passes, and then the cookie is expired. So my server shuts down the tunnel.I'm recognizing this expired cookie error at the Extension, and I'm stopping the tunnel as well.But because of the on-demand, the OS will call again to startTunnelWithOptions() and when it will fail (because of the expired cookie), it will call it again and again.It will be solved only when the user will open the app, and do some action to get another cookie.Is there a way to stop the onDemand from the Extension, even if the containing app is closed?If no - is there another solution to this problem?P.S - till now what I did was to display an alert

Hi there... Im looking for help getting a small Script Editor app to function properly.This app simply opens Safari and then clicks the Clear History... button so that each new session is started with a freshly cleaned browser.This action can be done manually but it is much quicker when using the script to do it.I've also made the same basic script to clear Safari and then quit Safari.Script Editor was used to make the script then save it as an application in the user Application folder.It was given Accessibility permissions and set up as a Service with a command key assigned to activate it.========Here is the issue that I'm stumbling upon.When I manually go trough the menus and select the Clear History button it actually does it.The History, the website data and the cookies and who knows what else are all cleared out as expected and I'm left with a fresh browser to use.But when the Script Editor script is used ... to click the exact same button, ....only the History is cleared. The website data and

I've added 2 new App Bundle Identifiers, and its been about 24+ hours and they still aren't appearing in App Store Connect for me to use with a new listing.I've tried logging out, deleting cookies, using alternate browser without luck.Anyone else having this issue?

Hi, I've encountered a problem on the device while trying to callWKWebsiteDataStore.default().httpCookieStore.getAllCookies() and got a message like :Could not signal service com.apple.WebKit.WebContent And the completion block didn't get called. So the our app is hanging on waiting for the responseThis should be listed as a bug for Apple since even though there's an error, the completion block should get called or should throw some error here. I don't know what caused the problem, I only tried to install and reinstall different buiild of the app, let me know if anyone knows how to resolve the issue. Thanks!

iOS 13 seemingly changed the way Safari handles their save password prompt. In pre-iOS 13, when Safari detected that a user successfully logged into a website, it would show the save password prompt and pause the loading of the site before it could proceed to the next page.Our implementation was unknowingly relying on this pause. Now in iOS 13, instead of pausing, Safari will continue to load the next page while the save password prompt sits in the foreground. This is normally not an issue for most situations since the next page that the user is being redirected to is most commonly another website which means Safari is still open and therefore so is the save password prompt. In our circumstance though, the login will redirect the user back into the app which closes Safari and the save password prompt along with it. This means the user has less than a second before the password prompt disappears.Does anyone have a solution to this? It would be great if the pre-iOS behavior could be reapplied somehow. Or if ano

An app I submitted was rejected, so I made the necessary changes. I had an extra in-app purchase, which I was not using and when I went to delete it, I deleted the wrong. Now, I have created a new in-app subscription to replace the one I deleted, but I can not submit it for review, it is stuck on Ready to Submit As soon as I click Submit for review, 1/2 second later, it automatically returns:There was an error saving changes. Please try again later. If the problem persists, please contact us.The 2 other in-app purchases are Waiting for Review.I clicked Submit In-App Purchase and the spinner is stuck spinning next to Submitting In-App Purchase.I have turned off my mac, deleted cookies, used different browsers, deleted and added the in-app purchase again and nothing is working.