ASWebAuthenticationSession cookie

I am using WKWebView inside my Swift App for SSO login. Now, SSO session is retained due to cookies saved. In Android there's an option to clear the cache or clear data from their settings Apps. Can I make my iOS App eligible for such a feature? I don't want to give an option inside my Application to clear the cache. is there any external option available which can be used for this inspite of Re-installing the application.

Question: Do App Clips support receiving callbacks from ASWebAuthentictionSession's redirectCallbackURL? Context: I'm trying to get CloudKit working in an app clip. Read support is done, but it would be nice for the user to see the capabilities before full download. Presently, I have the CloudKit Web Services successfully invoking redirectURL within SafariViewController, but I haven't figured out how to get it to direct to something the App Clip can get a hold of. CloudKit allows you to specify three different callbackURLs: https:// [freeform] http:// localhost[freeform] cloudkit-icloud.:// [freeform] I am new to AuthenticationSerivces framework so I may have missed something. The desired OAuth doesn't need to be CloudKit/iCloud but any provider. Everything is working except the redirect URL.

Hi there, I'd like to know how to stop sending/receiving Push Notifications when the user clear cookies in Safari, therefore the session / authentication cookie. The server will never learn the cookie was deleted and it will keep sending Push Notifications to the web client although the user will be logged out. Any thoughts? Thank you.

If you visit the website https://www.deutschlandfunk.de/ (or https://www.deutschlandfunkkultur.de/) with Safari and browse for a while inside that domain (duration is not fixed neither the amount of visited pages), images are not loaded any more (unless they are already in cache). It seems to be necessairy to use the back button while browsing to trigger that behaviour. This issue occurs using the Safari browser on Mac as well as on IPhones and IPads. On iOS it affects Firefox and Chrome too. As soon as the issue occurs, any new image (e.g. image is not in cache storage) will not be shown. A while can be a few hours. We were not able to find out any event that might be causing this issue. Cached Images will be shown. Using the inspector you can see, that the browser tries to load the images, but nothing happens. There is no error or warning. It seems, that the request is not fired at all. Copying the URL of an unloaded image to another browser tab does not load the image neither. Using another browser (on Mac

This is my manifest.json file for my safari extension that I've just developed: { manifest_version: 2, default_locale: en, name: BeTimeful, description: Never regret going to social media or YouTube again!, version: 1.0, icons: { 48: images/icon-48.png, 64: images/icon-64.png, 96: images/icon-96.png, 128: images/icon-128.png, 256: images/icon-256.png, 512: images/icon-512.png }, web_accessible_resources: [images/*, *], browser_action: { default_popup: popup/index.html, default_title: Betimeful, default_icon: { 16: images/toolbar-icon-16.png, 19: images/toolbar-icon-19.png, 32: images/toolbar-icon-32.png, 38: images/toolbar-icon-38.png, } }, background: { scripts: [Libraries/jquery.js,Libraries/raygun.min.js, js/background.js], persistent: true }, content_scripts: [ { matches: [ *://www.betimeful.com/cancel, *://www.betimeful.com/success ], js: [js/success.js] }, { matches: [*://calendar.google.com/*, http://blank.org/*], js: [ Libraries/jquery.js, Libraries/party.min.js, Libraries/popper.min.js, Libraries/boo

I have a video player that streams URLs coming from AWS using a signed cookie method. This works fine when streaming locally on the device, but does not work when attempting to AirPlay. I understand the reason why this is failing due to the AirPlay device not receiving the cookie. Is there a way to pass the cookie along with the AirPlay request? Are there other methods available to accomplish streaming via signed URLs?

In our Mac application, we are creating a web-socket connection using NWConnection and we are able to successfully establish the connection and read/write data from both sides. We have auth tokens which are sent in headers of NWProtocolWebSocket.Options to the server. If token is good, server accepts the web-socket connection. As per RFC 6455, if server does not want to accept the connection for any reason during web-socket handshake, it returns 403 status code. In our case, if cookies are not valid, server returns 403 during web-socket handshake. However, we could not find a way to read this status code in Network.framework. We are only getting failed state with NWErrorwhich is .posix(53) but there is no indication of the status code 403. We tried looking into protocol metadata on NWConnection object and they are nil. We tested the same using URLSessionWebSocketTask where in failure callback method, we could see 403 status code on task.response which means client is getting the code correctly from s