Search results for

“xcode github”

95,409 results found

Post

Replies

Boosts

Views

Activity

Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Quinn is helping this, which is great. I am just curious if the com.apple.developer.icloud- is really com.apple.developer.icloud-container-identifiers. I am guessing that the provisioning profile on your machine, either your notebook or Mac Mini, is not up to date, which leads to the different behaviors. Maybe you can try the following: Be sure your developer account is correctly set up in Xcode Settings > Apple Accounts, and your Mac has the access Apple's developer portal. Uncheck the Automatically manage signing box, and check it back. This tells Xcode to refresh the provisioning profile. If that doesn't help, try to remove the iCloud capability – You are not using any iCloud feature, and so don't really need the capability just yet. If you do need the iCloud capability, check one of the services, and pick an iCloud container if the service you checked is iCloud Documents or CloudKit. This is how folks use the capability. If everything goes well, the .entitlements file in your project
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
1w
.contactAccessPicker shows blank sheet on iOS 26.1
I’m running into an issue using .contactAccessPicker on a device running iOS 26.1 - a blank sheet appears instead of the expected Contact Access Picker. It works on: Simulator (iOS 26.0) Device + Simulator (iOS 18.6) The issue appears specific to real devices on iOS 26.0+. Environment: Device: iPhone 16 Pro iOS Versions Tested: 26.0 and 26.1 Xcode 26.0.1 SwiftUI app, deployment target: iOS 17+ @available(iOS 18.0, *) private var contactPicker: some View { contactsSettingsButton(Title) { showContactPicker = true } .contactAccessPicker(isPresented: $showContactPicker) { _ in Task { await contactManager.fetchContacts() showSelectContacts = true } } } Filed a Feedback: FB20929400 Is there a known workaround?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
7
0
319
1w
Cannot create new CloudKit container after deleting all containers - need help
I accidentally deleted all CloudKit containers from the CloudKit Database console, and now I'm unable to create new containers. Both the CloudKit Console website and Xcode are not allowing me to create any new containers. Is there a way to restore the deleted containers? How can I create a new CloudKit container if the console website is not responding? Thank you.
Topic: App & System Services SubTopic: iCloud & Data Tags:
2
0
84
1w
Reply to Data Disappeared
Thanks for taking the time to share your question here. After reading your question, I’m finding myself with more questions than answers right now. Could you tell me what database you’re using (SwiftData)? Also, please specify the programming languages, frameworks, or tools you’re working with. The more details you can share, including code snippets and the versions of the tools you’re using (like Xcode, macOS, iOS, etc.), the better. Lastly, could you let me know which platform you’re aiming for? I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.
Topic: Programming Languages SubTopic: Swift
1w
Can't specify platform version for xcodebuild download 26.x
Prior to iOS 26.0 we were able to download specific simulator runtimes from the command line by using a command like xcodebuild -downloadPlatform iOS -buildVersion 18.0 This is described in the documentation here. This no longer works for 26.x. If I run the following command: xcodebuild -downloadPlatform iOS -buildVersion 26.0 it fails with the following error: Finding content... iOS 26.0 is not available for download. If I omit the -buildVersion flag it will download the latest version, currently 26.2, but if I try and specify 26.2 as the buildVersion I still get iOS 26.2 is not available for download. This behavior has been confirmed on Xcode 26.2. Perhaps related, it appears these runtimes are also no longer being made available for download on https://developer.apple.com/download/all
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
377
1w
Reply to User crash report contains ??? instead of my app's symbols and no binary image base address
Thanks. I wasn't sure what I should use as the load address for the atos command. I used the start address of the __TEXT segment, but I just got the crash address back: % atos -arch x86_64 -o ~/Library/Developer/Xcode/Archives/2026-02-03/MyApp 03.02.2026, 13.48.xcarchive/dSYMs/MyApp.app.dSYM/Contents/Resources/DWARF/MyApp -l 0x10462e000 0x10844eb40 0x10844eb40 Although notice that the range of __TEXT 10462e000-1048c8000 doesn't even contain the crash address 0x10844eb40. Unless I'm doing something wrong, it looks to me like the crash is out of my control and I can't really do anything about it, which like you said is kind of confirmed by the weird crash report.
Topic: Developer Tools & Services SubTopic: General Tags:
1w
Reply to Current wisdom on multiple XPC services in a System Extension?
[quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] I wanted to confirm that this is the current best practice. [/quote] For an ES sysex, yes. As to what happens when you combine ES and NE, I did some digging and that text is definitely present in the Xcode 12.5 man page and definitely gone in the Xcode 13 one. Based on that info I was able to track down FB8701548, which was a developer request that we remove that limit. This was resolved in macOS 11 and, as part of that, we removed that text from the man page. Neat! With that in mind, let’s return to your other questions: [quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] should they each declare the Mach service name under their respective Info.plist keys? [/quote] That’s up to you. I can see arguments either way: If the ES and NE subsystems within your sysex are tightly bound together, it’d make sense to use a single named endpoint. OTOH, if those subsystems act independently, it’d make s
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Thanks for your answer. I want to clarify the situation. i use automatic signing with Signing & Capabilities editor at the moment iCloud is disabled and not used I have cleaned all derived data - no change. I have reinstalled Xcode - no change. I have delete the project and reloaded it from my git repository - no change. I have loaded the project on my MacBook. - and it compiles without any problem. I have no clue what difference between these to systems is.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
1w
Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
1w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
Topic: Machine Learning & AI SubTopic: Apple Intelligence Tags:
1w
isEligibleForAgeFeatures: wrong minimum OS version
Dear Apple, while implementing Declared Age Range API in my app, I've noticed a mistake in documentation: the isEligibleForAgeFeatures property is marked 26.0+ in documentation, but 26.2+ in Xcode, which ultimately leads to inability to use it with OS below 26.2. Moreover, I'm thoroughly confused by this quote from documentation: This flag returns true on iOS and iPadOS based on a person’s eligibility and always returns false on macOS. It leads me to two questions: Is it possible to use Declared Age Range API for macOS apps? Will it be possible to use it in future? Will there be any changes regarding this matter in a meantime (especially after Jan 1st)? If yes - when should we expect these changes? If no - why this API declares macOS 26+ support alongside iOS/iPadOS, if it simply doesn't work for macOS now? As of now, my iOS app works flawlessly with given API (on iOS 26.2) while macOS app returns isEligibleForAgeFeatures = false and requestAgeRange request always throws AgeRangeService.Error.notAvai
Topic: App & System Services SubTopic: General Tags:
1
0
276
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Quinn is helping this, which is great. I am just curious if the com.apple.developer.icloud- is really com.apple.developer.icloud-container-identifiers. I am guessing that the provisioning profile on your machine, either your notebook or Mac Mini, is not up to date, which leads to the different behaviors. Maybe you can try the following: Be sure your developer account is correctly set up in Xcode Settings > Apple Accounts, and your Mac has the access Apple's developer portal. Uncheck the Automatically manage signing box, and check it back. This tells Xcode to refresh the provisioning profile. If that doesn't help, try to remove the iCloud capability – You are not using any iCloud feature, and so don't really need the capability just yet. If you do need the iCloud capability, check one of the services, and pick an iCloud container if the service you checked is iCloud Documents or CloudKit. This is how folks use the capability. If everything goes well, the .entitlements file in your project
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
1w
.contactAccessPicker shows blank sheet on iOS 26.1
I’m running into an issue using .contactAccessPicker on a device running iOS 26.1 - a blank sheet appears instead of the expected Contact Access Picker. It works on: Simulator (iOS 26.0) Device + Simulator (iOS 18.6) The issue appears specific to real devices on iOS 26.0+. Environment: Device: iPhone 16 Pro iOS Versions Tested: 26.0 and 26.1 Xcode 26.0.1 SwiftUI app, deployment target: iOS 17+ @available(iOS 18.0, *) private var contactPicker: some View { contactsSettingsButton(Title) { showContactPicker = true } .contactAccessPicker(isPresented: $showContactPicker) { _ in Task { await contactManager.fetchContacts() showSelectContacts = true } } } Filed a Feedback: FB20929400 Is there a known workaround?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
7
Boosts
0
Views
319
Activity
1w
Cannot create new CloudKit container after deleting all containers - need help
I accidentally deleted all CloudKit containers from the CloudKit Database console, and now I'm unable to create new containers. Both the CloudKit Console website and Xcode are not allowing me to create any new containers. Is there a way to restore the deleted containers? How can I create a new CloudKit container if the console website is not responding? Thank you.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
2
Boosts
0
Views
84
Activity
1w
Reply to Cannot create new CloudKit container after deleting all containers - need help
Just to add that the steps to bring back a hidden container are detailed in this post, and that you can add a new container from Xcode as well, as detailed in Enabling CloudKit in Your App. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
Boosts
Views
Activity
1w
Reply to Data Disappeared
Thanks for taking the time to share your question here. After reading your question, I’m finding myself with more questions than answers right now. Could you tell me what database you’re using (SwiftData)? Also, please specify the programming languages, frameworks, or tools you’re working with. The more details you can share, including code snippets and the versions of the tools you’re using (like Xcode, macOS, iOS, etc.), the better. Lastly, could you let me know which platform you’re aiming for? I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.
Topic: Programming Languages SubTopic: Swift
Replies
Boosts
Views
Activity
1w
Can't specify platform version for xcodebuild download 26.x
Prior to iOS 26.0 we were able to download specific simulator runtimes from the command line by using a command like xcodebuild -downloadPlatform iOS -buildVersion 18.0 This is described in the documentation here. This no longer works for 26.x. If I run the following command: xcodebuild -downloadPlatform iOS -buildVersion 26.0 it fails with the following error: Finding content... iOS 26.0 is not available for download. If I omit the -buildVersion flag it will download the latest version, currently 26.2, but if I try and specify 26.2 as the buildVersion I still get iOS 26.2 is not available for download. This behavior has been confirmed on Xcode 26.2. Perhaps related, it appears these runtimes are also no longer being made available for download on https://developer.apple.com/download/all
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
377
Activity
1w
Reply to Ad Hoc .ipa for iOS 12.5.8
Same issue, add hoc build compiled with Xcode 26 cannot be run on iOS 12. No crash report only logs. Launch screen is shown for a second and in a moment app is closed
Topic: Business & Education SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Xcode 26 fails to load SPM packages
Enabling IDEPackageSupportUseBuiltinSCM worked perfectly! Even better than with old Xcode versions.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
1w
Reply to User crash report contains ??? instead of my app's symbols and no binary image base address
Thanks. I wasn't sure what I should use as the load address for the atos command. I used the start address of the __TEXT segment, but I just got the crash address back: % atos -arch x86_64 -o ~/Library/Developer/Xcode/Archives/2026-02-03/MyApp 03.02.2026, 13.48.xcarchive/dSYMs/MyApp.app.dSYM/Contents/Resources/DWARF/MyApp -l 0x10462e000 0x10844eb40 0x10844eb40 Although notice that the range of __TEXT 10462e000-1048c8000 doesn't even contain the crash address 0x10844eb40. Unless I'm doing something wrong, it looks to me like the crash is out of my control and I can't really do anything about it, which like you said is kind of confirmed by the weird crash report.
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Current wisdom on multiple XPC services in a System Extension?
[quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] I wanted to confirm that this is the current best practice. [/quote] For an ES sysex, yes. As to what happens when you combine ES and NE, I did some digging and that text is definitely present in the Xcode 12.5 man page and definitely gone in the Xcode 13 one. Based on that info I was able to track down FB8701548, which was a developer request that we remove that limit. This was resolved in macOS 11 and, as part of that, we removed that text from the man page. Neat! With that in mind, let’s return to your other questions: [quote='818568021, rsfinn_halcyon, /thread/818568, /profile/rsfinn_halcyon'] should they each declare the Mach service name under their respective Info.plist keys? [/quote] That’s up to you. I can see arguments either way: If the ES and NE subsystems within your sysex are tightly bound together, it’d make sense to use a single named endpoint. OTOH, if those subsystems act independently, it’d make s
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Provisioning profile missing entitlement: com.apple.developer.icloud
Thanks for your answer. I want to clarify the situation. i use automatic signing with Signing & Capabilities editor at the moment iCloud is disabled and not used I have cleaned all derived data - no change. I have reinstalled Xcode - no change. I have delete the project and reloaded it from my git repository - no change. I have loaded the project on my MacBook. - and it compiles without any problem. I have no clue what difference between these to systems is.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
1w
Dumb noob question,,
How can i get a simple figma layout with minimal art into xcode
Topic: Developer Tools & Services SubTopic: Xcode
Replies
1
Boosts
0
Views
63
Activity
1w
Reply to Unable to install Metal toolchain through Xcode Cloud
removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
Boosts
Views
Activity
1w
Reply to New project with new AppIntent throws build error
To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer
Topic: Machine Learning & AI SubTopic: Apple Intelligence Tags:
Replies
Boosts
Views
Activity
1w
isEligibleForAgeFeatures: wrong minimum OS version
Dear Apple, while implementing Declared Age Range API in my app, I've noticed a mistake in documentation: the isEligibleForAgeFeatures property is marked 26.0+ in documentation, but 26.2+ in Xcode, which ultimately leads to inability to use it with OS below 26.2. Moreover, I'm thoroughly confused by this quote from documentation: This flag returns true on iOS and iPadOS based on a person’s eligibility and always returns false on macOS. It leads me to two questions: Is it possible to use Declared Age Range API for macOS apps? Will it be possible to use it in future? Will there be any changes regarding this matter in a meantime (especially after Jan 1st)? If yes - when should we expect these changes? If no - why this API declares macOS 26+ support alongside iOS/iPadOS, if it simply doesn't work for macOS now? As of now, my iOS app works flawlessly with given API (on iOS 26.2) while macOS app returns isEligibleForAgeFeatures = false and requestAgeRange request always throws AgeRangeService.Error.notAvai
Topic: App & System Services SubTopic: General Tags:
Replies
1
Boosts
0
Views
276
Activity
1w