ASWebAuthenticationSession cookie

The issue has been resolved. There was some additional layer of cookies access protection on our website and it blocked reading cookie with CRSF token. There is no issue within WebKit and iOS then. Thread can be closed :)

Can you please file this through Feedback Assistant, ideally with a screen recording and/or repro case? ASWebAuthenticationSession uses WKNavigationDelegate under the hood, so it should be able to catch all the same things.

The additionalHeaderFields value follows the Fetch standard's forbidden request header algorithm. Cookie is one of the forbidden fields.

Interestingly, I left a simulator running for a long while and came back to my desk and hit the authenticate button. The Safari view caused by using ASWebAuthenticationSession came up, was blank/invalid, and I got a callback from the authentication provider.. The header that caused this was: Location: myapp://auth#state=17A26C7A-AFDE-4C3B-BA89-85FAA343F0DB&error=invalid_request_object&error_description=Expired%20jwt I'm partially happy it worked at least once, but am also confused it doesn't work when it should

This is going to be a problem for a lot of people and we probably need to raise developer awareness Previously the setting would cause the Mac Address to rotate each time you connect to a wifi network; turn it off stopped that and your hardware address would be used (or perhaps the random one just stayed the same). Now for iOS and MacOS there no way to stop it rotating each time you connect to anything. The new on/off switch controls whether the address rotates while you are still connected after XX minutes. This is an absolute disaster for the following situations: Networks where you want to pin a device to an IP address via DHCP Reservations so that you can QoS traffic going to that device. Networks were you want to lock children to an IP Address so that you can parent control what those kids can do on the internet. AirPlane and Hotel Hot Spots that you buy 5 hours of usage at high speed that link to your mac address Networks with really Long DHCP lease times to ensure stablility will find that Apple Device

@Knyhuus an identical function similar to what you have in the scope of the .navigationDestination(for:) closure would be: @ViewBuilder func itemViewFor(destination: Destination) -> some View { switch destination { case .cookie: CookieView() case .milk: MilkView() } } Secondly, StateObject property wrapper should be marked private and instantiated with the View.

TESTABLE CODE: public enum Destination: String, Codable, Hashable { case cookie = Cookie 🍪 case milk = Milk 🥛 } final class Router: ObservableObject { @Published var navPath = NavigationPath() func navigate(to destination: Destination) { navPath.append(destination) print(||| Router: add to navPath: (navPath.count)) } func navigateBack() { guard navPath.count > 0 else { return } navPath.removeLast() print(||| Router: remove from navPath: (navPath.count)) } func navigateToRoot() { guard navPath.count > 1 else { return } navPath.removeLast(navPath.count) } } struct RootView: View { @ObservedObject var router = Router() var body: some View { NavigationStack(path: $router.navPath) { List { Button(action: { router.navigate(to: .cookie) }, label: { Text(Destination.cookie.rawValue) }) Button(action: { router.navigate(to: .milk) }, label: { Text(Destination.milk.rawValue) }) } .navigationBarBackButtonHidden() .navigationDestination(for: Destination.self) { destination in let _ = pri

Tracking App Store sales from partner promotions is tough because most affiliate platforms still depend on cookies. I encountered this challenge myself, so I developed a SaaS platform to tackle it. You can now set up affiliate programs in minutes, monitor sales, and effortlessly pay commissions to your partners. Interested? Connect with me on LinkedIn: https://www.linkedin.com/in/tonipeinoit I'm here to help you get started. Best of luck!