Search results for

“xcode github”

96,040 results found

Post

Replies

Boosts

Views

Activity

Reply to App Crash with mxSignpost function not found
Just a quick update… I’m confidant that we now have a handle on this issue (FB22384135). I can’t offer any concrete details about timelines but, as always, I encourage you to test with the latest betas as we seed them. And in this case that means Xcode betas, because this is an Xcode issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Apr ’26
NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
I'm implementing a NEDNSProxyProvider on macOS 15.x and macOS 26.x. The flow works correctly up to the last step — returning the DNS response to the client via writeDatagrams. Environment: macOS 15.x, 26.x Xcode 26.x NEDNSProxyProvider with NEAppProxyUDPFlow What I'm doing: override func handleNewFlow(_ flow: NEAppProxyFlow) -> Bool { guard let udpFlow = flow as? NEAppProxyUDPFlow else { return false } udpFlow.readDatagrams { datagrams, endpoints, error in // 1. Read DNS request from client // 2. Forward to upstream DNS server via TCP // 3. Receive response from upstream // 4. Try to return response to client: udpFlow.writeDatagrams([responseData], sentBy: [endpoints.first!]) { error in // Always fails: The datagram was too large // responseData is 50-200 bytes — well within UDP limits } } return true } Investigation: I added logging to check the type of endpoints.first : // On macOS 15.0 and 26.3.1: // type(of: endpoints.first) → NWAddressEndpoint // Not NWHostEndpoint as expected On both macOS 1
Topic: App & System Services SubTopic: Networking Tags:
7
0
228
Apr ’26
Reply to Updating Apps on the AppStore no longer working for me.
What version of Swift Playground are you using? And is this on Mac or iPad? [quote='821471021, GMacD53, /thread/821471, /profile/GMacD53'] because Playground does not use Xcode as far as I am aware? [/quote] Yes and no. It’s an independent product but, when you submit to App Store Connect, it reuses a bunch of the same infrastructure. Thus it’s not a huge surprise that you’re seeing Xcode in this error message. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Apr ’26
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. I also created a brand-new Xcode 26.4 project and enabled the Enhanced Security capability there. Xcode generated these two entitlements as String values (1 and 2) by default in the new project as well. So at least in my current Xcode 26.4 / OS 26.4 environment, the string-based form appears to be both the Xcode default and the only form that launches normally in testing.
Topic: Code Signing SubTopic: Entitlements Tags:
Apr ’26
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. So at least in my current Xcode 26.4 / OS 26.4 environment, the Boolean form appears to break launch, while the string-based form works normally.
Topic: Code Signing SubTopic: Entitlements Tags:
Apr ’26
Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
2
0
373
Apr ’26
Can't start Ad Hoc .ipa for iOS 12
Hi, We're having problems starting an Ad Hoc ipa on an iPad with iOS 12.7.7 and 12.7.8. The iPad's UUID has been added to the provisioning profile. The iPad that we are trying to start the app on is online, so Apple's certificate validation server should be reachable. We don't have any problems with iOS versions above iOS 12. The .ipa was built using the latest version of Xcode (26.2, build 17C52). Here is the anonymised and reduced console log (only the app launch / bootstrap part): default 07:29:35.683108+0100 SpringBoard Icon touch began: default 07:29:35.752640+0100 SpringBoard Icon tapped: default 07:29:35.768538+0100 trustd cert[0]: SubjectCommonName =(leaf)[]> 0 default 07:29:35.791500+0100 SpringBoard Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] default 07:29:35.793654+0100 trustd cert[0]: IssuerCommonName =(path)[]> 0 default 07:29:36.043497+0100 assertiond Submitting new job for on behalf of SpringBoard (pid: 48) default 07:29:36.044393+0100 Sprin
Topic: Business & Education SubTopic: General Tags:
4
0
2.0k
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
@Manuel_Apps I am in the same situation... the current version of my app on the App Store is defunct for iOS 12 people. I am now working on a build with target iOS 15. As soon as it’s submitted and released I am planning on making the broken release unavailable. This way iOS 12 users have to uninstall the broken version so they can reinstall the (still working) version before that. I totally agree with you. I wish Xcode 16 (the first Xcode that did not support iOS 12 anymore) would have prevented me from building the app with the unsupported target. Instead it was waved through without warning. Yes, the Xcode support page said it didn’t support iOS 12, yet there was no hard stop. I was not aware I was sitting on a time bomb for at least 1 year. I thought only debugging was not supported but building was -- because it worked. The broken app happened a few days ago when my customer was holding an event in front of an audience, some of which had iOS 12 on their iPads. One can imagine t
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Apr ’26
Reply to iOS 12.5.8 fails to bootstrap app
Thanks @Manuel_Apps and @BioDranik for your metoo’s. In the meantime I have received a response from dev support. They gave me the same answer that is found in the thread pointed to by @DTS Engineer . This is the tech part of the answer: When you submit to the App Store, Apple modifies your binary. They strip your signature, encrypt the binary and re-sign it. This encryption alters the Mach-O file's page alignments and load commands. Nothing I can do about that. I’m fine with progress but I wish Xcode would have somehow prevented me from using the unsupported deployment target. Ever since Xcode 16 (which also does not support iOS 12) I thought my target was ok. So I will bump the target to iOS 15 (for now, in the future possibly higher). Since my app in the App Store is defunct for iOS 12 users I will upload a build with target iOS 15 and then mark the broken build as unavailable (App Connect > Pricing and Availability). This way the legacy users will get the last working version.
Topic: App & System Services SubTopic: General Tags:
Apr ’26
iOS 12.5.8 fails to bootstrap app
Hello, I released a new build for my app but it fails to run on iOS 12.5.8 (tested on iPad Air, iPhone 6, iPhone 5s). The launch storybard is shown, then the app stops abruptly. There is no crash log. It runs fine on iOS 13 or higher. Xcode 26.3 was showing a call stack (something with UIView) that did not include any app code. Now with Xcode 26.4 (and its new command line tools) there is an info popup with a debug metadata dump. However, I don’t intend to focus on Xcode here because it officially does not support iOS 12. It’s ok if I cannot debug, I just want the app to run on the device like the previous build did. Since there is no crash log, and the console is showing a bootstrap error, I believe my app code has not been executed and is therefore not at fault. Build 674 released on 23-Mar-2026: worked fine on iOS 12, built with Xcode 26.3 Build 675 released on 29-Mar-2026: Bootstrap error as described, with both Xcode 26.3 and 26.4 Deployment target = 12.4 Trie
Topic: App & System Services SubTopic: General Tags:
5
0
388
Apr ’26
Reply to In-App Purchase dialog not appearing during App Review but works on physical device
Has anyone experienced a similar situation where IAP works on device but fails during App Review? Any suggestions on what might be different in the review environment? Apple reviews your In-App Purchases in the sandbox environment, the same environment you use to test your products. In the sandbox, StoreKit uses data you configured for your app in App Store Connect when the app calls StoreKit APIs in the environment. Be sure to test your products in the sandbox before submitting them for review. If your app uses a StoreKit configuration file, be sure to disable StoreKit Testing in Xcode before starting to test in the sandbox. For more information, see Setting up StoreKit Testing in Xcode. After you successfully test your products in the sandbox, be sure to submit them for review in App Store Connect. For more information, see Submit an In-App Purchase.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Apr ’26
Reply to App Crash with mxSignpost function not found
Just a quick update… I’m confidant that we now have a handle on this issue (FB22384135). I can’t offer any concrete details about timelines but, as always, I encourage you to test with the latest betas as we seed them. And in this case that means Xcode betas, because this is an Xcode issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
I'm implementing a NEDNSProxyProvider on macOS 15.x and macOS 26.x. The flow works correctly up to the last step — returning the DNS response to the client via writeDatagrams. Environment: macOS 15.x, 26.x Xcode 26.x NEDNSProxyProvider with NEAppProxyUDPFlow What I'm doing: override func handleNewFlow(_ flow: NEAppProxyFlow) -> Bool { guard let udpFlow = flow as? NEAppProxyUDPFlow else { return false } udpFlow.readDatagrams { datagrams, endpoints, error in // 1. Read DNS request from client // 2. Forward to upstream DNS server via TCP // 3. Receive response from upstream // 4. Try to return response to client: udpFlow.writeDatagrams([responseData], sentBy: [endpoints.first!]) { error in // Always fails: The datagram was too large // responseData is 50-200 bytes — well within UDP limits } } return true } Investigation: I added logging to check the type of endpoints.first : // On macOS 15.0 and 26.3.1: // type(of: endpoints.first) → NWAddressEndpoint // Not NWHostEndpoint as expected On both macOS 1
Topic: App & System Services SubTopic: Networking Tags:
Replies
7
Boosts
0
Views
228
Activity
Apr ’26
Reply to Updating Apps on the AppStore no longer working for me.
What version of Swift Playground are you using? And is this on Mac or iPad? [quote='821471021, GMacD53, /thread/821471, /profile/GMacD53'] because Playground does not use Xcode as far as I am aware? [/quote] Yes and no. It’s an independent product but, when you submit to App Store Connect, it reuses a bunch of the same infrastructure. Thus it’s not a huge surprise that you’re seeing Xcode in this error message. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Can’t paste into Simulator after updating to Xcode 26.4
I can't recall the exact Xcode version but this issue has occurred in the past, but was isolated to older simulator runtimes. This time it looks like affecting both 26.4 and previous simulators. One has to wonder how the same feature gets repeatedly fixed and then broken again.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. I also created a brand-new Xcode 26.4 project and enabled the Enhanced Security capability there. Xcode generated these two entitlements as String values (1 and 2) by default in the new project as well. So at least in my current Xcode 26.4 / OS 26.4 environment, the string-based form appears to be both the Xcode default and the only form that launches normally in testing.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values (1 and 2), and the app immediately launched normally again. So at least in my current Xcode 26.4 / OS 26.4 environment, the Boolean form appears to break launch, while the string-based form works normally.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
For reference, I’m attaching screenshots of: the App Review message that says these entitlements must be boolean and true, and the Xcode 26.4 release note section that says to use the new -string variants with values 1 and 2. These are the two pieces of guidance I’m trying to reconcile.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Apr ’26
Unable to submit for App Review
Hi. I’m unable submit to a new Version of my App. If i want to Add for Review, i get the Error Message: “Unable to Add for Review The items below are required to start the review process: This build is using a beta version of Xcode and can’t be submitted.” The new Version is Uploaded from the Latest Version of Swift Playground for iPad(4.7). No Betas
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
2
Boosts
0
Views
373
Activity
Apr ’26
Reply to Login to App Store in VM not possible
Could you download Xcode from the https://developer.apple.com/download/applications/ outside of the VM and then transfer it to the VM?
Topic: Developer Tools & Services SubTopic: Xcode
Replies
Boosts
Views
Activity
Apr ’26
Login to App Store in VM not possible
I'm running a macOS 15.2 guest on a macOS 15.1.1 host with UTM. I'm trying to install Xcode from within the App Store but cannot login to the App Store. When I enter credentials and click 'Sign In' I get the Error 'An unknown error occurred'.
Topic: Developer Tools & Services SubTopic: Xcode
Replies
2
Boosts
0
Views
338
Activity
Apr ’26
Can't start Ad Hoc .ipa for iOS 12
Hi, We're having problems starting an Ad Hoc ipa on an iPad with iOS 12.7.7 and 12.7.8. The iPad's UUID has been added to the provisioning profile. The iPad that we are trying to start the app on is online, so Apple's certificate validation server should be reachable. We don't have any problems with iOS versions above iOS 12. The .ipa was built using the latest version of Xcode (26.2, build 17C52). Here is the anonymised and reduced console log (only the app launch / bootstrap part): default 07:29:35.683108+0100 SpringBoard Icon touch began: default 07:29:35.752640+0100 SpringBoard Icon tapped: default 07:29:35.768538+0100 trustd cert[0]: SubjectCommonName =(leaf)[]> 0 default 07:29:35.791500+0100 SpringBoard Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName] default 07:29:35.793654+0100 trustd cert[0]: IssuerCommonName =(path)[]> 0 default 07:29:36.043497+0100 assertiond Submitting new job for on behalf of SpringBoard (pid: 48) default 07:29:36.044393+0100 Sprin
Topic: Business & Education SubTopic: General Tags:
Replies
4
Boosts
0
Views
2.0k
Activity
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
@Manuel_Apps I am in the same situation... the current version of my app on the App Store is defunct for iOS 12 people. I am now working on a build with target iOS 15. As soon as it’s submitted and released I am planning on making the broken release unavailable. This way iOS 12 users have to uninstall the broken version so they can reinstall the (still working) version before that. I totally agree with you. I wish Xcode 16 (the first Xcode that did not support iOS 12 anymore) would have prevented me from building the app with the unsupported target. Instead it was waved through without warning. Yes, the Xcode support page said it didn’t support iOS 12, yet there was no hard stop. I was not aware I was sitting on a time bomb for at least 1 year. I thought only debugging was not supported but building was -- because it worked. The broken app happened a few days ago when my customer was holding an event in front of an audience, some of which had iOS 12 on their iPads. One can imagine t
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to iOS 12.5.8 fails to bootstrap app
Thanks @Manuel_Apps and @BioDranik for your metoo’s. In the meantime I have received a response from dev support. They gave me the same answer that is found in the thread pointed to by @DTS Engineer . This is the tech part of the answer: When you submit to the App Store, Apple modifies your binary. They strip your signature, encrypt the binary and re-sign it. This encryption alters the Mach-O file's page alignments and load commands. Nothing I can do about that. I’m fine with progress but I wish Xcode would have somehow prevented me from using the unsupported deployment target. Ever since Xcode 16 (which also does not support iOS 12) I thought my target was ok. So I will bump the target to iOS 15 (for now, in the future possibly higher). Since my app in the App Store is defunct for iOS 12 users I will upload a build with target iOS 15 and then mark the broken build as unavailable (App Connect > Pricing and Availability). This way the legacy users will get the last working version.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
iOS 12.5.8 fails to bootstrap app
Hello, I released a new build for my app but it fails to run on iOS 12.5.8 (tested on iPad Air, iPhone 6, iPhone 5s). The launch storybard is shown, then the app stops abruptly. There is no crash log. It runs fine on iOS 13 or higher. Xcode 26.3 was showing a call stack (something with UIView) that did not include any app code. Now with Xcode 26.4 (and its new command line tools) there is an info popup with a debug metadata dump. However, I don’t intend to focus on Xcode here because it officially does not support iOS 12. It’s ok if I cannot debug, I just want the app to run on the device like the previous build did. Since there is no crash log, and the console is showing a bootstrap error, I believe my app code has not been executed and is therefore not at fault. Build 674 released on 23-Mar-2026: worked fine on iOS 12, built with Xcode 26.3 Build 675 released on 29-Mar-2026: Bootstrap error as described, with both Xcode 26.3 and 26.4 Deployment target = 12.4 Trie
Topic: App & System Services SubTopic: General Tags:
Replies
5
Boosts
0
Views
388
Activity
Apr ’26
Reply to In-App Purchase dialog not appearing during App Review but works on physical device
Has anyone experienced a similar situation where IAP works on device but fails during App Review? Any suggestions on what might be different in the review environment? Apple reviews your In-App Purchases in the sandbox environment, the same environment you use to test your products. In the sandbox, StoreKit uses data you configured for your app in App Store Connect when the app calls StoreKit APIs in the environment. Be sure to test your products in the sandbox before submitting them for review. If your app uses a StoreKit configuration file, be sure to disable StoreKit Testing in Xcode before starting to test in the sandbox. For more information, see Setting up StoreKit Testing in Xcode. After you successfully test your products in the sandbox, be sure to submit them for review in App Store Connect. For more information, see Submit an In-App Purchase.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
Apr ’26