xcode github

Thanks for the post and thank you for bringing this issue to our attention. Indeed, this is a known problem where SwiftUI control will need to resize a window with a NavigationSplitView generates Invalid view geometry warnings in Xcode. The issue is currently being investigated. If you would like to be notified when the fix is implemented and Xcode ceases to issue these warnings, we recommend filing a bug report. The warning looks something like this: Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to.. In the meantime, please be advised that the engineering team is actively addressing the warning issue. If you want to file a bug please post the FB number h

To test with Xcode you have to run a local server. https://developer.apple.com/documentation/backgroundassets/testing-asset-packs-locally

Thanks for the post. Are you using Flutter? Have you addressed by the support channel for Flutter - the third-party resource you are using. Unless another developer in the forums has experience with the third-party and can provide assistance. However I am sure the 3rd party tool could be aware of the issue if you provide them with crash files. Have you been able to reproduce on your environment? The objective-c code you posted seems ok, is that the part of the code is crashing? Have you use Xcode to reproduce it? Thanks Albert Pascual
  Worldwide Developer Relations.

@viktor_runcoach thanks for letting me know, I didn't see the issue when I use Xcode 26.2 beta and the simulator for iPhone Air, but it means I need to get a real device and start trying to reproduce it. However is very important if you can file a bug using a focus sample showing the issue. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Above all, thanks for providing all this. Looking forward your bug to get to the bottom of the issue. Albert Pascual
  Worldwide Developer Relations.

As you’ve noticed, Swift Playground currently doesn’t support the iOS 26 SDK. We understand that there’s strong demand for that, but I can’t offer any advice as to when it’ll happen. If you need you use iOS 26 SDK features right now, your only real option is to create your playground with Xcode. Make sure to create an app playground, as explained on Developer > Swift Student Challenge > Get ready. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Albert, I have downloaded Xcode 26.2 (17C48), the issue exists and is isolated to the iPhone Air. Both iPhone Air 26.2 and 26.1 simulators have this issue. Other simulators on Xcode 26.2 remain free of this issue. Let me know if there is additional information I can provide.

Hi Albert, Thank you for the links. After reviewing both documentation pages, I've implemented a complete test following the specifications, but password autofill is not working. Test Implementation AASA File (accessible at http://localhost:8080/.well-known/apple-app-site-association): { webcredentials: { apps: [ZW962TGA3F.com.test.PasswordAutofillTest] } } ✅ Served with Content-Type: application/json ✅ Verified accessible via curl ✅ Team ID matches Apple Developer account Associated Domains Entitlement: webcredentials:localhost:8080 ✅ Configured in both Debug and Release entitlements ✅ Bundle ID: com.test.PasswordAutofillTest SwiftUI Implementation: TextField(Email, text: $email) .textContentType(.username) SecureField(Password, text: $password) .textContentType(.password) Authentication Flow: App sends POST to http://localhost:8080/login with credentials Server returns 200 OK App displays Login successful Server logs confirm request received and processed Result ❌ No Save Password prompt appears ❌ No autofi

I'm having the same issue here, even with Xcode 26.2 RC. The hang occurs when you navigate to a second view within any tab view.

Hmmm, that wasn’t the answer I was expecting. Something is clearly borked on your machine. You wrote: [quote='868691022, swdev-sos, /thread/809359?answerId=868691022#868691022, /profile/swdev-sos'] Does the pkgbuild command have a cache that can be deleted? [/quote] AFAIK that’s not the case. [quote='868691022, swdev-sos, /thread/809359?answerId=868691022#868691022, /profile/swdev-sos'] We are both using [Xcode] 16.2. [/quote] The Xcode version doesn’t matter here, but rather the OS version. Are you both on the same version of macOS? If you create a new user account on your Mac, does the problem reproduce there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sorry I didn’t reply sooner; older versions of DevForums had a bug that meant that I didn’t see updates on this thread (that’s fixed now, so yay!). [quote='785947022, Najjii, /thread/675290?answerId=785947022#785947022, /profile/Najjii'] edit the trust settings to be able to use it normally. [/quote] Monkeying with trust settings on a code-signing certificate is a bad idea. It can trigger the dreaded errSecInternalComponent. I talk more about this in Fixing an untrusted code signing certificate. [quote='794668022, olvrwn, /thread/675290?answerId=794668022#794668022, /profile/olvrwn'] Is there any information why this does not work with iCloud Keychain? [/quote] Not really. Keychain Access is very much on the way out as a user-level feature. Witness, for example, its recent move from Applications > Utilities to /System/Library/CoreServices/Applications. Given that, it’s easy to see why big picture issues like this aren’t being addressed. Having said that, the file-based keychain is also on its way out, as e

Any updates on supporting Apple Silicon? I've been using Xcode Cloud for a long time but current build times are unacceptable and we're considering switching to other providers.