ASWebAuthenticationSession cookie

Just made up a small Radio Player (more just a playlist Player with only one Play Button) for some friends of mine in pure HTML 5, CSS3 and JavaScript and Node JS. Now I want to change the JS Code Logic into a Swift 5 to have all that as an iOS App. If you go on the page radiodorfdepp.de you first have to pass the age verification, next you can just click one button which changes the picture and plays randomly songs from an array of mp3 files. This works fine on an ordinary desktop browser and on androids, but not on iOS. There the screen dimms a bit down after the click and nothing gets played. My main question is: how can I make a button in swift 5 which plays the click sound, starts a random song from the playlist, plays the songs, which are saved in an array, continuously and randomly on and on..And, what is one of the most crucial points: does not turns the iOS Gadget into this strange dimming mode ? Is there anybody out there who hast the nerves and skills to tell me how to swiftify my JS Code into a an

Just made up a small Radio Player (more just a playlist Player with only one Play Button) for some friends of mine in pure HTML 5, CSS3 and JavaScript and Node JS. Now I want to change the JS Code Logic into a Swift 5 to have all that as an iOS App. If you go on the page radiodorfdepp.de you first have to pass the age verification, next you can just click one button which changes the picture and plays randomly songs from an array of mp3 files. This works fine on an ordinary desktop browser and on androids, but not on iOS. There the screen dimms a bit down after the click and nothing gets played. My main question is: how can I make a button in swift 5 which plays the click sound, starts a random song from the playlist, plays the songs, which are saved in an array, continuously and randomly on and on..And, what is one of the most crucial points: does not turns the iOS Gadget into this strange dimming mode ? Is there anybody out there who hast the nerves and skills to tell me how to swiftify my JS Code into a an

Hi! We’re having an issue with the new App Store Connect dSYMs API in one of our automatic process. We’re obtaining dSYMs download URL through app’s build data to upload it to Bugsnag. We noticed something that can be considered a bug, it is a consistency problem that occurs when using that service to obtain the .zip file that contains the dSYMs, always trying to hit it through our API returns 401 (bad signature). But this gets fixed (starts always returning 200 in the API) once we use a generated URL (from the build-bundle request) for that release in a browser (tested in postman, chrome or safari, incognito mode or not). Was there any similar report or case? Is it a known issue? Are there any extra considerations when using this URL, such as cookies, user agent, etc? Thanks!

I've developed a ios safari web extension for my app and everything seemed to work fine in the simulator and on my device. However, I've noticed that in some cases when the user tries to give permission to the extension inside safari, the system displays an alert asking for permissions to all the sites saved in the user's keychain. It's really strange. I've not been able to always reproduce this behavior, sometimes it works normally and it asks for permission just for the domain where the user is on. The issue has become a real problem when I've discovered that when the user has a lot of saved passwords for sites in the keychain, the Safari freezes when asking for permission and becomes absolutely unusable, forcing the user to close it. Here is the manifest for my extension: { manifest_version: 2, content_security_policy: script-src 'self' https://ssl.google-analytics.com; object-src 'self', background: { scripts: [ browser-polyfill.js, background.js ], persistent: false }, content_scripts: [{ js: [ browser-p

Ever since upgrading to Monterey 12.2 beta, Safari will hang up trying to access google.com. This worked ok until the upgrade. Right now it's sat there for 10 minutes, and still hasn't accessed it. By contrast, when I use firefox it finds that website instantly. Any suggestions about debugging this, apart from the sledgehammer approach of deleting all cookies and history (which is lame to say the least).

We're using webview in our iOS app to show the web page. The website contains cookies and they need to be Accepted/Declined by the users by clicking on Accept or Decline button, Which is handled by the website. Apple asked us to either remove the cookies from web content or implement App Tracking Transparency. We added App Tracking Transparency and now the user is asked to allow or deny the tracking permission once the user allows then we show the cookie prompt in the webview and if they deny the permission we don't show the cookie prompt. To achieve this we've set one cookie when the user denies the permission - so that the cookie popup isn't shown. But our app still got rejected, below is the message by the apple review team - We noticed you collect data to track after the user selects Ask App Not to Track on the App Tracking Transparency permission request. Specifically, we noticed your app accesses web content you own and collects cookies for

My team has developed a Glide app (web app, not a native iPhone app) that can be saved to the home page and accessed like an actual app. In our Glide app, we have an embedded other app, that requires the Safari settings to allow cookies and not prevent cross-site tracking in order to work. When these settings are turned on for Safari, and users access our app in Safari directly, the embedded app works fine. However for the users who saved our app to home screen and access it that way, even if they allow cookies and turn off prevent cross-site tracking in Safari settings, the embedded app does not load. Is there any workaround for this? If not Safari, what browser is the app that has been saved to the home screen using? Why does it have separate settings from normal Safari?

Are there scoping issues with document.cookie in Safari? I have written a javascript constructor function around document.cookie. The constructor function is defined in the global scope but is used inside of another object instance. It works in Firefox and Chrome but does not work in Safari. If I do window.onload = function() { var ck = 'test=this; max-age=600; domain=localhost; path=/dev_lab_current/lab_56; SameSite=Lax'; document.cookie = ck; } it works. But it does not set the cookie in my html application. The application has a host object constructor that creates an instance of the cookie manager constructor within it. So it is about 2 scope levels deep. But the exact same code DOES work in Firefox and Chrome. The html is designed to allow hard coded records to be kept for cookies created by it. PHP is used to write the hard coded records in a javascript source code file. For this reason I would not post a demo on my publically available web site. Thank you for time and attenti

I have a SwiftUI app live on the App Store which uses ASWebAuthenticationSession to authenticate against several remote services. It all runs perfectly on iOS but I'm getting a stream of complaints from users running it on Monterey / Catalyst. There seem to be 2 main errors: The auth browser window doesn't anchor properly, so the window will pop-up but it's completely independent of my app, so can easily end-up behind my application (which then appears to have hung) Even worse, on some machines (mostly m1 iMacs) the window doesn't pop-up at all but the OAuth request to the browser sits in some queue somewhere and at a later point when the user happens to restart their browser they will be prompted to login for every single time they clicked on the sign in button in my app. I've seen lots of other reports of the 2nd problem which just seems to happen randomly so I don't have a repro. I've seen a similar number of different ways of implementing ASWebAuthenticationPresentationContextProviding which (I p

My app has access to some webviews, each webview opens a different page of the same website that has the cookie banner. I tought that the cookie banner would be enough for apple because the app doesn't actually track users, it's the website that does that. Apple rejected my App because of this, so I'm trying to find a way to incorporate the App Tracking Transparency but I can't find what I should do in the case the user disables the tracking, what is the correct behaviour that the app should have? If I give the user access to the web do I still need to implement App Tracking Transparency? If not, would giving the option on a corner of the webview be enough or should I make the user choose where to open the pages before the actual webview shows?

Hello, I have an intermittent problem that shows up when a user taps a Universal Link that opens my app. I've got a WKWebView with a stored authentication cookie. Normally when the app runs the cookie is loaded from the locksmith storage and put into the webview's cookies. When the webview accesses the web app, the web app knows the user is authenticated. When the app is brought to the foreground, a Javascript call is evaluated in the webview. Scenario: App has been used and the user is no longer in it. Time passes -- maybe a night? User gets an email with a Universal Link and taps on it. App opens, loads the link in the webview, and gets the unauthenticated version. App sends the movedToForeground Javascript call and gets an error: JavaScript execution returned a result of an unsupported type. Error is captured and an app alert pops up asking if the user wants to reload. User taps reload and gets the login form (again showing webview is not authenticated). I can't easily reproduce

Hi I'm developing a captive portal with cookies, it works fine in devices like Macs, laptops and android devices but cookies don't work on iPhone. I'm creating cookies in js with document.cookie but the problem is when I connect my iPhone and close CNA, it destroy them and next time I try to connect, cookies don't exist anymore. Someone can help me to figure out how can I avoid CNA destroy my cookies?