The Xcode CLI bundled git version is 2.39.3 which is affected by a critical security flaw: Recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution I can install, update and use git in the terminal from another source/path, but the Xcode app is still using the built-in Xcode CLI path which is still affected by this security flaw. Will you update the git version in Xcode anytime soon?

We are having massive problems and seriously random bugs when building our app after upgrading to Sequoia and Xcode16. For example: suddenly .sheets reload when you swipe the app to the background/foreground and the performance is really bad with massive input lag on buttons and actions. All of this worked fine when built in Xcode 15.4. But by far the worst is that we can't even archive the app anymore. We just get a "Command SwiftCompile failed with a nonzero exit code." when the builder is trying to compile the main project. No other message, no information at all. After many hours of debugging and narrowing it down to a single view with another .sheet(item:) we can "fix" it by changing the item in the sheet to another struct somehow. Ok so we can archive now, but the app is still unusable because of the performance issues. How are we going about this? How are we supposed to build our app now? We can't even run Xcode 15.4 anymore because we have Sequoia. Is this the Apple developer experience with random bugs that is randomly fixed every Xcode update?

We need to append some values in the User-Agent HTTP header for our SSO flows. We use the ASWebAuthenticationSession class as you should, but I can't find any information on how to modify the headers in this web view. I have tried setting the "global" user agent via UserDefaults.standard.register(defaults: ["UserAgent": "fakeUserAgent"]) While it does change the User-Agent in WKWebView, it seemingly does not impact the ASWebAuthenticationSession. There are also no configuration settings to change headers or User-Agent on ASWebAuthenticationSession. Is it not possible by security design?