Xcode

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.

@viktor_runcoach and @howard_kang , thanks for both post, so when we have 2 reports is good to compare the issue. Both are using the iPhone Air simulator with iOS 26.1 and both are on Xcode 26.1. Am I correct? https://developer.apple.com/forums/thread/809465?answerId=868722022#868722022 Can you please download Xcode 26.2 beta and try exactly the same thing? Lets get to the bottom of this issue. Albert Pascual
  Worldwide Developer Relations.

Even with XCode Version 26.2 beta (17C5013i) iOS 26.2 beta (23C5027e) I am receiving Value of type 'AgeRangeService' has no member 'isEligibleForAgeFeatures' as an error on the provided code. public func testEligible() async { do { let response = try await AgeRangeService.shared.isEligibleForAgeFeatures // Handle response if response { print([K]: Eligible for age features.) } else { print([K]: Not eligible for age features.) } } catch { print([K]: Fail to check eligibility for age features.) } }

Thanks for your post. It seems like you have everything working. So you do not see the autofill behavior after following this documentation? https://developer.apple.com/documentation/security/password-autofill Can you provide me a link to your AASA file showing how you have defined the web credentials for the app? https://developer.apple.com/documentation/Xcode/supporting-associated-domains Example: webcredentials: { apps: [ ABCDE12345.com.example.app ] }, Looking forward to your reply. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post and the code. I run the code in the iPhone air simulator using Xcode 26.2 beta and I don't see the hang. Can you share the way to reproduce it? Also will be help you to share a focused sample app with all the settings you are using. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

Hello @JoshuaLin, Can you provide a screenshot of the MLPackage view in Xcode? --Greg

Thank you for your reply. Unfortunately, creating a package using productbuild results in the same zero-byte file written to /Applications. I used the command: productbuild --sign --component /Applications Interestingly, if my coworker creates the application on his machine, I can then use his application in my pkgbuild script and the installation succeeds. Both his application and the application I build on my machine are signed with the same company Developer ID Application and are notarized. Both applications also run on my machine and have the same functionality, as their source was pulled from the same branch. We are both using XCode 16.2. This problem only started to happen on my machine last week. Does the pkgbuild command have a cache that can be deleted? Thank you for your time.

[quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] I already feel bad asking you again [/quote] No worries. It gives me a good excuse to brush up on my debugging skills (-: [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. [/quote] Bah. This isn’t super surprising, and it’s the sort of thing I’d know if I had an iPhone 17 to play with. It’s definitely time to ping my boss about that. [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] Unfortunately, I didn't really understand where/what to look for in Xcode. [/quote] OK. Lemme run you through a non-MTE example: Using Xcode 26.1 on macOS 15.7.1, I created an iOS app with two buttons wired up to these two methods: var memory: UnsafeMutableRawPointer? = nil func mallocAction() { self.memory = malloc(1024) } func freeAction() { free(self.memory) } In the scheme