Search results for

“xcode github”

96,036 results found

Post

Replies

Boosts

Views

Activity

Reply to Using mTLS with YubiKey via USB-C and PIV
An update: when I remove ALL of my keychain groups except for com.apple.token (i.e. I removed the one for pivtoken), it works ONLY WITH my enterprise provisioning profile. For some reason, xcode is OK with me manually modifying my .entitlement file to remove the app prefix ID that xcode is automatically adding. If I use my own personal account, xcode is NOT OK with me modifying the provisioning profile to remove the app prefix from com.apple.token (xcode says my provisioning profile doesn't match the entitlements file's value for the keychain-access-groups entitlement. ) I'd like to get it working in both scenatios. Is there something I can do in xcode to make my automatically-managed one work?
Topic: Privacy & Security SubTopic: General Tags:
Apr ’26
Background UDP receive for lighting control (Art-Net/sACN)
I'm developing a lighting control app for iOS that receives Art-Net (UDP port 6454) and sACN (UDP port 5568) packets from a lighting console and relays commands to BLE wristbands with LEDs. This is used in live event production — the participant locks their phone while in a show and expects lighting control to continue uninterrupted. The problem UDP receive stops reliably ~30 seconds after the screen locks. I understand this is by design - iOS suspends apps in the background. However, I'm trying to understand if any supported path exists for this use case. What I've already tried UIRequiresPersistentWiFi = true - helps with Wi-Fi association but doesn't prevent app suspension Silent AVAudioEngine loop with UIBackgroundModes: audio - keeps the app alive, works in testing, but risks App Store rejection and feels like an abuse of the audio background mode NWListener (Network framework) on the UDP port - same suspension behaviour Socket rebind on applicationWillEnterForeground - recovers after resume but doesn't
1
0
84
Apr ’26
Reply to Using mTLS with YubiKey via USB-C and PIV
@DTS Engineer Quinn, Thank you for your reply; I think I'm on a better path now. Unfortunately, I'm now getting an -34018 error and nil with the code below: var result: CFTypeRef? let status = SecItemCopyMatching([ kSecClass: kSecClassCertificate, kSecAttrAccessGroup: kSecAttrAccessGroupToken, kSecMatchLimit: kSecMatchLimitAll, kSecReturnRef: true, ] as CFDictionary, &result) print(status=(status) result=(String(describing: result))) I've tried your trouble shooting steps mentioned in your other posts, including printing out my app's entitlements, and they all look correct: application-identifier MY_APP_ID.MY_APP_BUNDLE_ID com.apple.developer.default-data-protection NSFileProtectionComplete com.apple.developer.team-identifier MY_APP_ID com.apple.security.application-groups get-task-allow keychain-access-groups MY_APP_ID.com.apple.token MY_APP_ID.com.apple.pivtoken MY_APP_ID.MY_APP_BUNDLE_ID I've tried both an xcode-managed provisioning profile, and an enterprise one owned by my org, and n
Topic: Privacy & Security SubTopic: General Tags:
Apr ’26
SKStoreReviewController requestReviewInScene: does not display review prompt in debug builds on iOS 26.5 beta (23F5043k)
[SKStoreReviewController requestReviewInScene:] no longer displays the review prompt in debug/development builds on iOS 26.5 beta (23F5043k and 23F5043g). According to Apple's documentation, the review prompt should always appear in debug builds to facilitate testing. This was working in previous iOS versions (iOS 26.4 and older). Steps to reproduce: Run app from Xcode in debug configuration on a device running iOS 26.5 beta (23F5043k or 23F5043g) Call [SKStoreReviewController requestReviewInScene:windowScene] with a valid, foreground-active UIWindowScene Observe that the method executes without error (scene is valid per NSLog) but no review prompt appears Expected: Review prompt should display in debug builds Actual: No prompt appears, despite the scene being valid and foreground-active This worked correctly on previous iOS versions (26.4) so looks like this bug was introduced in 26.5 Beta versions. I have already filed a bug report in Feedback Assistant with number: FB22445620
4
0
326
Apr ’26
First-time notarization submissions stuck "In Progress" for 24+ hours — Electron app
Hi, All notarization submissions for our new Electron macOS app have been stuck in In Progress for over 24 hours, with no logs available. Environment: Team ID: T7632V8V2D Certificate: Developer ID Application (valid, identity 83AC47F44D984509D5530439DD32729076B84982) Tool: xcrun notarytool submit (Xcode CLI) App: Electron 33, signed with hardened runtime, entitlements include allow-jit and allow-unsigned-executable-memory File: zip of .app (~236MB for arm64, ~104MB for x64) codesign --verify --deep --strict passes with no issues Apple System Status shows Developer ID Notary Service: Available Stuck submissions (all In Progress, no logs available): ea0fd8d4-1f2d-4266-aa84-aa3f3ba9a8fb (Apr 8, 09:40 UTC) dfaacdd2-1a11-4844-b8b7-b07bae809a7b (Apr 7, 16:49 UTC) 8256e1f0-e501-4423-8744-35b5b78ec87f (Apr 7, 10:32 UTC) a477d536-d84a-4c25-99ca-d125e0a22de1 (Apr 7, 09:07 UTC) This is our first time notarizing any app on this developer account. We understand first-time submissions may be routed to in-depth ana
1
0
275
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this. AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test: Using the same Xcode, create a new project from the iOS > App template. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B). In Signing & Capabilities, make sure automatic code signing is enabled for all configurations. And that the correct team is selected. At the top, make sure that you have a test device selected as the run destination. Then add the Contactless Pass Provisioning (SharableCredential) capability. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish. Assuming that works, try running the app on a test device. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ App
Apr ’26
Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We are seeing what looks like a signing / managed-capability mismatch for Contactless Pass Provisioning. Environment Team ID: S7AUTD2C2B Bundle IDs: com.swiftpass.ios com.swiftpass.ios.dev Xcode: 26.4 macOS: 26.4 Problem Our app has had Contactless Pass Provisioning approved by Apple for a long time, and builds were working until a few days ago. Without any intentional signing/capability changes on our side, Xcode started failing with the following error: Provisioning profile Swiftpass prod Appstore doesn't include the Contactless Pass Provisioning capability. Contactless Pass Provisioning capability needs to be assigned to your team and bundle identifier by Apple in order to be included in a profile. Observed behavior Xcode marks the relevant provisioning profiles as Ineligible in the profile selector. This affects both development/debug and release/App Store builds. If we remove Contactless Pass Provisioning from the app entitlements/capabilities, the exact same profiles immediate
27
0
1.6k
Apr ’26
Team ID "" is not associated with an active membership
I’m blocked from building an iOS app because Apple Developer Portal says my Team ID is not associated with an active membership. On the Apple Developer portal resources page I see: “Team ID: ‘’ is not associated with an active membership.” I don’t see a Team selector in the Developer portal (only Account / Help / Sign out). The portal shows a banner “Join the Apple Developer Program”. When I click it: “Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership.” In App Store Connect → Users and Access, the only user is my Apple ID and it shows: Role: Account Holder, Admin Apps: All Apps Because of this, my iOS build/signing fails (Expo/EAS build, but same in Xcode) with: Provisioning profile doesn’t support Push Notifications capability Provisioning profile doesn’t include the aps-environment entitlement I enabled Push Notifications / tried regenerating provisioning profiles, but it keeps reusing the same old App Store profile and fails. Que
2
0
160
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
Ok, here is my step by step (what I think is) a solution guide... (worked for me) Fix: Xcode Hangs on macOS Tahoe 26.4 (SDKs Status Unavailable) The Problem macOS Tahoe 26.4 introduces a bug where a CoreSimulator subprocess (simdiskimaged) repeatedly exceeds its 20MB memory limit and gets killed by the system. This causes CoreSimulatorService to hang indefinitely, which in turn causes Xcode to freeze, SDKs to show status unavailable, and all simulators to become inaccessible. The root cause is a runaway loop that creates new SimRuntimeBundle files every 11 seconds in /Library/Developer/CoreSimulator/Cryptex/Images/mnt/, bloating the state that simdiskimaged must load on startup beyond its jetsam memory limit. The Fix Step 1 — Grant Terminal Full Disk Access The files that need to be deleted are protected by TCC (Transparency, Consent, and Control). Without this step, sudo rm will return Operation not permitted. Open System Settings → Privacy & Security → Full Disk Access Click the + butt
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
Here is a summary of my findings so far working with AI: The Bug: macOS Tahoe 26.4 triggers a loop in the CoreSimulator subsystem where a new SimRuntimeBundle is created in /Library/Developer/CoreSimulator/Cryptex/Images/mnt/ every 11 seconds. This accumulates thousands of files and bloats the images.plist manifest. Why Xcode Hangs: When Xcode launches, it starts CoreSimulatorService, which spawns a helper daemon called simdiskimaged via XPC. simdiskimaged is responsible for managing simulator disk images and runtimes. On startup, it tries to load and validate the entire contents of images.plist and the Cryptex directory. Because of the runaway loop, there are now 7,000+ files and a bloated manifest to parse. simdiskimaged exceeds its hardcoded 20MB jetsam memory limit and gets killed by the system (SIGKILL/-9). CoreSimulatorService sent a synchronous XPC message to simdiskimaged and is now waiting for a reply that will never come — it hangs forever on mach_msg2_trap. Everything downstream h
Apr ’26
Reply to Could not launch app on watchOS downloaded from TestFlight
Thanks, I believe you also sent a code level support request? The watch as the error “untrusted” occurs when the app provisioning profile is missing. Have you deployed the app using Xcode? I requested the sysdiagnose from you to check on the untrusted app trying to launch. Thanks Albert
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Apr ’26
Reply to Using mTLS with YubiKey via USB-C and PIV
An update: when I remove ALL of my keychain groups except for com.apple.token (i.e. I removed the one for pivtoken), it works ONLY WITH my enterprise provisioning profile. For some reason, xcode is OK with me manually modifying my .entitlement file to remove the app prefix ID that xcode is automatically adding. If I use my own personal account, xcode is NOT OK with me modifying the provisioning profile to remove the app prefix from com.apple.token (xcode says my provisioning profile doesn't match the entitlements file's value for the keychain-access-groups entitlement. ) I'd like to get it working in both scenatios. Is there something I can do in xcode to make my automatically-managed one work?
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Background UDP receive for lighting control (Art-Net/sACN)
I'm developing a lighting control app for iOS that receives Art-Net (UDP port 6454) and sACN (UDP port 5568) packets from a lighting console and relays commands to BLE wristbands with LEDs. This is used in live event production — the participant locks their phone while in a show and expects lighting control to continue uninterrupted. The problem UDP receive stops reliably ~30 seconds after the screen locks. I understand this is by design - iOS suspends apps in the background. However, I'm trying to understand if any supported path exists for this use case. What I've already tried UIRequiresPersistentWiFi = true - helps with Wi-Fi association but doesn't prevent app suspension Silent AVAudioEngine loop with UIBackgroundModes: audio - keeps the app alive, works in testing, but risks App Store rejection and feels like an abuse of the audio background mode NWListener (Network framework) on the UDP port - same suspension behaviour Socket rebind on applicationWillEnterForeground - recovers after resume but doesn't
Replies
1
Boosts
0
Views
84
Activity
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
I've run into the same issue as you. I also tried installing Xcode 26.4, Can you please share the any resolution ?
Replies
Boosts
Views
Activity
Apr ’26
Reply to Using mTLS with YubiKey via USB-C and PIV
@DTS Engineer Quinn, Thank you for your reply; I think I'm on a better path now. Unfortunately, I'm now getting an -34018 error and nil with the code below: var result: CFTypeRef? let status = SecItemCopyMatching([ kSecClass: kSecClassCertificate, kSecAttrAccessGroup: kSecAttrAccessGroupToken, kSecMatchLimit: kSecMatchLimitAll, kSecReturnRef: true, ] as CFDictionary, &result) print(status=(status) result=(String(describing: result))) I've tried your trouble shooting steps mentioned in your other posts, including printing out my app's entitlements, and they all look correct: application-identifier MY_APP_ID.MY_APP_BUNDLE_ID com.apple.developer.default-data-protection NSFileProtectionComplete com.apple.developer.team-identifier MY_APP_ID com.apple.security.application-groups get-task-allow keychain-access-groups MY_APP_ID.com.apple.token MY_APP_ID.com.apple.pivtoken MY_APP_ID.MY_APP_BUNDLE_ID I've tried both an xcode-managed provisioning profile, and an enterprise one owned by my org, and n
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
I've run into the same issue as you. I also tried installing Xcode 26.3, and opening the project with the older version did work once. But for some reason the same problem reappeared later, and using 26.3 no longer helps.
Replies
Boosts
Views
Activity
Apr ’26
SKStoreReviewController requestReviewInScene: does not display review prompt in debug builds on iOS 26.5 beta (23F5043k)
[SKStoreReviewController requestReviewInScene:] no longer displays the review prompt in debug/development builds on iOS 26.5 beta (23F5043k and 23F5043g). According to Apple's documentation, the review prompt should always appear in debug builds to facilitate testing. This was working in previous iOS versions (iOS 26.4 and older). Steps to reproduce: Run app from Xcode in debug configuration on a device running iOS 26.5 beta (23F5043k or 23F5043g) Call [SKStoreReviewController requestReviewInScene:windowScene] with a valid, foreground-active UIWindowScene Observe that the method executes without error (scene is valid per NSLog) but no review prompt appears Expected: Review prompt should display in debug builds Actual: No prompt appears, despite the scene being valid and foreground-active This worked correctly on previous iOS versions (26.4) so looks like this bug was introduced in 26.5 Beta versions. I have already filed a bug report in Feedback Assistant with number: FB22445620
Replies
4
Boosts
0
Views
326
Activity
Apr ’26
First-time notarization submissions stuck "In Progress" for 24+ hours — Electron app
Hi, All notarization submissions for our new Electron macOS app have been stuck in In Progress for over 24 hours, with no logs available. Environment: Team ID: T7632V8V2D Certificate: Developer ID Application (valid, identity 83AC47F44D984509D5530439DD32729076B84982) Tool: xcrun notarytool submit (Xcode CLI) App: Electron 33, signed with hardened runtime, entitlements include allow-jit and allow-unsigned-executable-memory File: zip of .app (~236MB for arm64, ~104MB for x64) codesign --verify --deep --strict passes with no issues Apple System Status shows Developer ID Notary Service: Available Stuck submissions (all In Progress, no logs available): ea0fd8d4-1f2d-4266-aa84-aa3f3ba9a8fb (Apr 8, 09:40 UTC) dfaacdd2-1a11-4844-b8b7-b07bae809a7b (Apr 7, 16:49 UTC) 8256e1f0-e501-4423-8744-35b5b78ec87f (Apr 7, 10:32 UTC) a477d536-d84a-4c25-99ca-d125e0a22de1 (Apr 7, 09:07 UTC) This is our first time notarizing any app on this developer account. We understand first-time submissions may be routed to in-depth ana
Replies
1
Boosts
0
Views
275
Activity
Apr ’26
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this. AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test: Using the same Xcode, create a new project from the iOS > App template. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B). In Signing & Capabilities, make sure automatic code signing is enabled for all configurations. And that the correct team is selected. At the top, make sure that you have a test device selected as the run destination. Then add the Contactless Pass Provisioning (SharableCredential) capability. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish. Assuming that works, try running the app on a test device. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ App
Replies
Boosts
Views
Activity
Apr ’26
Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We are seeing what looks like a signing / managed-capability mismatch for Contactless Pass Provisioning. Environment Team ID: S7AUTD2C2B Bundle IDs: com.swiftpass.ios com.swiftpass.ios.dev Xcode: 26.4 macOS: 26.4 Problem Our app has had Contactless Pass Provisioning approved by Apple for a long time, and builds were working until a few days ago. Without any intentional signing/capability changes on our side, Xcode started failing with the following error: Provisioning profile Swiftpass prod Appstore doesn't include the Contactless Pass Provisioning capability. Contactless Pass Provisioning capability needs to be assigned to your team and bundle identifier by Apple in order to be included in a profile. Observed behavior Xcode marks the relevant provisioning profiles as Ineligible in the profile selector. This affects both development/debug and release/App Store builds. If we remove Contactless Pass Provisioning from the app entitlements/capabilities, the exact same profiles immediate
Replies
27
Boosts
0
Views
1.6k
Activity
Apr ’26
Team ID "" is not associated with an active membership
I’m blocked from building an iOS app because Apple Developer Portal says my Team ID is not associated with an active membership. On the Apple Developer portal resources page I see: “Team ID: ‘’ is not associated with an active membership.” I don’t see a Team selector in the Developer portal (only Account / Help / Sign out). The portal shows a banner “Join the Apple Developer Program”. When I click it: “Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership.” In App Store Connect → Users and Access, the only user is my Apple ID and it shows: Role: Account Holder, Admin Apps: All Apps Because of this, my iOS build/signing fails (Expo/EAS build, but same in Xcode) with: Provisioning profile doesn’t support Push Notifications capability Provisioning profile doesn’t include the aps-environment entitlement I enabled Push Notifications / tried regenerating provisioning profiles, but it keeps reusing the same old App Store profile and fails. Que
Replies
2
Boosts
0
Views
160
Activity
Apr ’26
Reply to Xcode 26 – Organizer does not show “App Store Connect” for watchOS standalone app (only Release Testing available)
has there been any update to this? This is still happening on latest xcode
Replies
Boosts
Views
Activity
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
Ok, here is my step by step (what I think is) a solution guide... (worked for me) Fix: Xcode Hangs on macOS Tahoe 26.4 (SDKs Status Unavailable) The Problem macOS Tahoe 26.4 introduces a bug where a CoreSimulator subprocess (simdiskimaged) repeatedly exceeds its 20MB memory limit and gets killed by the system. This causes CoreSimulatorService to hang indefinitely, which in turn causes Xcode to freeze, SDKs to show status unavailable, and all simulators to become inaccessible. The root cause is a runaway loop that creates new SimRuntimeBundle files every 11 seconds in /Library/Developer/CoreSimulator/Cryptex/Images/mnt/, bloating the state that simdiskimaged must load on startup beyond its jetsam memory limit. The Fix Step 1 — Grant Terminal Full Disk Access The files that need to be deleted are protected by TCC (Transparency, Consent, and Control). Without this step, sudo rm will return Operation not permitted. Open System Settings → Privacy & Security → Full Disk Access Click the + butt
Replies
Boosts
Views
Activity
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
Here is a summary of my findings so far working with AI: The Bug: macOS Tahoe 26.4 triggers a loop in the CoreSimulator subsystem where a new SimRuntimeBundle is created in /Library/Developer/CoreSimulator/Cryptex/Images/mnt/ every 11 seconds. This accumulates thousands of files and bloats the images.plist manifest. Why Xcode Hangs: When Xcode launches, it starts CoreSimulatorService, which spawns a helper daemon called simdiskimaged via XPC. simdiskimaged is responsible for managing simulator disk images and runtimes. On startup, it tries to load and validate the entire contents of images.plist and the Cryptex directory. Because of the runaway loop, there are now 7,000+ files and a bloated manifest to parse. simdiskimaged exceeds its hardcoded 20MB jetsam memory limit and gets killed by the system (SIGKILL/-9). CoreSimulatorService sent a synchronous XPC message to simdiskimaged and is now waiting for a reply that will never come — it hangs forever on mach_msg2_trap. Everything downstream h
Replies
Boosts
Views
Activity
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
As diniska wrote, this is what finally worked for me: Force quit Xcode rm /Library/Developer/CoreSimulator/Images/images.plist Wait 1-2 minutes Launch Xcode You do need to reboot in recovery, turn off SIP, do the deletion, reboot in recovery, turn on SIP, and reboot. But it's been working ever since.
Replies
Boosts
Views
Activity
Apr ’26