Search results for

“xcode github”

96,040 results found

Post

Replies

Boosts

Views

Activity

‌Xcode26-built apps cannot run on iPhone 6 or earlier devices‌
‌Using Xcode 26, the built package encounters device compatibility issues — while it installs successfully on supported iPhone devices, but it crashes immediately upon launch and cannot run normally.‌‌In previous versions of Xcode, the same minimum deployment setting in the project did not cause such compatibility issues.‌ The app built with Xcode 26 shows the following behavior when installed and tested on various devices:‌ iPhone6p iOS12.5.8 fails to run 2.iPhone6 iOS11 fails to run 3.Iphone6 iOS12.5.7 fails to run 4.iPhone7 iOS12.1.3 ok 5.iPhoneX iOS 12.2 ok 6.iphone6s plus iOS10.3.1 ok 7.iphoneXS. iOS 12.1.4 ok 8.iPhone11 iOS 13.6.1 ok 9.iPhone7. iOS 13.7 ok We have tested and found that an iPhone 6s Plus running iOS 10.3.1 can normally run the app. We would like to know whether apps built with Xcode 26 are inherently incompatible with iPhone 6 and older devices. Has Xcode 26’s underlying build environment removed full support for the A8 chip, resulting in bina
10
0
865
Apr ’26
Reply to StoreKit returns empty product list in Sandbox (TestFlight, valid IAP setup)
Can a first subscription be fetched in the sandbox before submitting an app version for review? Does the “Finalize before submission” state prevent StoreKit visibility, even in sandbox? Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. Additional information: the same subscription works correctly with StoreKit local testing in Xcode (StoreKit configuration file). The product is returned and the purchase flow behaves as expected. When you enable a configuration file in your Xcode project, this file becomes active. StoreKit uses data saved in the active configuration file when your app calls StoreKit APIs in the test environment. For more information, see Setting up StoreKit Testing in Xcode. To test in the sandbox, you must disable StoreKit Testing in Xcode in your Xcode project. This enables StoreKit to use data you configured for your app in App Store Connect when the app calls StoreKit APIs in th
Apr ’26
Reply to iOS 12.5.8 fails to bootstrap app
The same for Organic Maps: internal CI TestFlight build on March 25 works on iOS 12 device, the same binary with a few string resource changes, built on March 26 does not work. Built with the frozen version of Xcode 26.2. That implies some kind of Apple involvement when builds are uploaded.
Topic: App & System Services SubTopic: General Tags:
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
Thanks for the clarification. However, this is quite concerning from a developer and user-impact perspective. This app version was: • successfully built and uploaded with Xcode 16.4 • accepted in App Review • distributed through the App Store Despite having a deployment target of iOS 12, the build is now crashing on launch for all iOS 12 users, without any prior warning during submission or review. As a result, a previously working user base on iOS 12 has effectively lost access to the app overnight after updating, which is a significant regression in functionality. If iOS 15 is now a strict requirement for App Store distribution, it would be much safer for developers if: • the upload was rejected at submission time, or • a clear warning was shown before release rather than allowing distribution of a build that cannot run on supported devices declared in the app’s deployment target. Is there any recommended way to: Restore functionality for existing iOS 12 users (e.g. keep last compatible version ava
Apr ’26
App targeting iOS 12 crashes on launch when installed via TestFlight but works via Ad Hoc and Xcode direct install
My app targets iOS 12.0 and crashes immediately on launch when installed via TestFlight on an iPad running iOS 12.x. The same archive works perfectly when installed via Ad Hoc distribution or directly from Xcode. This is a regression — the exact same source code, compiled with the same Xcode version, was successfully distributed via TestFlight and the App Store last month (March 2026) without issues. No changes were made to the code, Xcode version, or signing configuration. Steps to reproduce: Archive an app with IPHONEOS_DEPLOYMENT_TARGET = 12.0 using Xcode 16.4 Upload to App Store Connect Install via TestFlight on an iPad running iOS 12.x App crashes immediately on launch (pre-main, no crash log generated) Expected: App launches normally (as it did last month) Actual: App is killed immediately, process exits with reason: (none) Console.app shows the process never transitions from xpcproxy to the actual binary — it dies within ~260ms of
1
0
176
Apr ’26
Reply to Xcode 26 fails to load SPM packages
@patrick Thanks for the post and providing a workaround, have you tried Xcode 26.5 beta without the workaround? Can you let me know if that works well for you? Anyone in this thread has filed a bug for this? If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Apr ’26
Unwanted Communication Reporting extension crash
I'm trying to implement Unwanted SMS and Calls reporting in an app I'm doing in my idle time. If I place a UITextField or UITextView inside a ILClassificationUIExtensionViewController, every time I select on such control the extension crashes without any logs. The closet idea I have on why it crashes it has something to do with iOS requesting the dictation feature. I'm using the latest (beta 8 at the time) iOS 16.0 beta on my iPhone 13 pro. Attaching my code here if you want to try for yourself: github
11
0
2.4k
Apr ’26
Apple watch Xcode pairing & connection issues
I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only
19
0
2.1k
Apr ’26
‌Xcode26-built apps cannot run on iPhone 6 or earlier devices‌
‌Using Xcode 26, the built package encounters device compatibility issues — while it installs successfully on supported iPhone devices, but it crashes immediately upon launch and cannot run normally.‌‌In previous versions of Xcode, the same minimum deployment setting in the project did not cause such compatibility issues.‌ The app built with Xcode 26 shows the following behavior when installed and tested on various devices:‌ iPhone6p iOS12.5.8 fails to run 2.iPhone6 iOS11 fails to run 3.Iphone6 iOS12.5.7 fails to run 4.iPhone7 iOS12.1.3 ok 5.iPhoneX iOS 12.2 ok 6.iphone6s plus iOS10.3.1 ok 7.iphoneXS. iOS 12.1.4 ok 8.iPhone11 iOS 13.6.1 ok 9.iPhone7. iOS 13.7 ok We have tested and found that an iPhone 6s Plus running iOS 10.3.1 can normally run the app. We would like to know whether apps built with Xcode 26 are inherently incompatible with iPhone 6 and older devices. Has Xcode 26’s underlying build environment removed full support for the A8 chip, resulting in bina
Replies
10
Boosts
0
Views
865
Activity
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
We used Xcode 26.2 to successfully build iOS 12 apps before March 25. After that, the same code crashes on iOS 12 at startup. It would be great if Apple officially confirms if it drops iOS 12 support in such a weird way, or if it was an issue that can be resolved.
Replies
Boosts
Views
Activity
Apr ’26
Reply to StoreKit returns empty product list in Sandbox (TestFlight, valid IAP setup)
Can a first subscription be fetched in the sandbox before submitting an app version for review? Does the “Finalize before submission” state prevent StoreKit visibility, even in sandbox? Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. Additional information: the same subscription works correctly with StoreKit local testing in Xcode (StoreKit configuration file). The product is returned and the purchase flow behaves as expected. When you enable a configuration file in your Xcode project, this file becomes active. StoreKit uses data saved in the active configuration file when your app calls StoreKit APIs in the test environment. For more information, see Setting up StoreKit Testing in Xcode. To test in the sandbox, you must disable StoreKit Testing in Xcode in your Xcode project. This enables StoreKit to use data you configured for your app in App Store Connect when the app calls StoreKit APIs in th
Replies
Boosts
Views
Activity
Apr ’26
Reply to Login to App Store in VM not possible
Would be useful if this worked. Without the xcode stuff the VM would be useless for me.
Replies
Boosts
Views
Activity
Apr ’26
Reply to iOS 12.5.8 fails to bootstrap app
The same for Organic Maps: internal CI TestFlight build on March 25 works on iOS 12 device, the same binary with a few string resource changes, built on March 26 does not work. Built with the frozen version of Xcode 26.2. That implies some kind of Apple involvement when builds are uploaded.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
Thanks for the clarification. However, this is quite concerning from a developer and user-impact perspective. This app version was: • successfully built and uploaded with Xcode 16.4 • accepted in App Review • distributed through the App Store Despite having a deployment target of iOS 12, the build is now crashing on launch for all iOS 12 users, without any prior warning during submission or review. As a result, a previously working user base on iOS 12 has effectively lost access to the app overnight after updating, which is a significant regression in functionality. If iOS 15 is now a strict requirement for App Store distribution, it would be much safer for developers if: • the upload was rejected at submission time, or • a clear warning was shown before release rather than allowing distribution of a build that cannot run on supported devices declared in the app’s deployment target. Is there any recommended way to: Restore functionality for existing iOS 12 users (e.g. keep last compatible version ava
Replies
Boosts
Views
Activity
Apr ’26
Reply to App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
Distribution through the App Store requires a minimum deployment target of iOS 15. For future reference, you can find this information listed on the Xcode Support webpage.
Replies
Boosts
Views
Activity
Apr ’26
App targeting iOS 12 crashes on launch when installed via TestFlight but works via Ad Hoc and Xcode direct install
My app targets iOS 12.0 and crashes immediately on launch when installed via TestFlight on an iPad running iOS 12.x. The same archive works perfectly when installed via Ad Hoc distribution or directly from Xcode. This is a regression — the exact same source code, compiled with the same Xcode version, was successfully distributed via TestFlight and the App Store last month (March 2026) without issues. No changes were made to the code, Xcode version, or signing configuration. Steps to reproduce: Archive an app with IPHONEOS_DEPLOYMENT_TARGET = 12.0 using Xcode 16.4 Upload to App Store Connect Install via TestFlight on an iPad running iOS 12.x App crashes immediately on launch (pre-main, no crash log generated) Expected: App launches normally (as it did last month) Actual: App is killed immediately, process exits with reason: (none) Console.app shows the process never transitions from xpcproxy to the actual binary — it dies within ~260ms of
Replies
1
Boosts
0
Views
176
Activity
Apr ’26
Reply to App targeting iOS 12 crashes on launch when installed via TestFlight but works via Ad Hoc and Xcode direct install
Distribution through the App Store requires a minimum deployment target of iOS 15. For future reference, you can find this information listed on the Xcode Support webpage.
Replies
Boosts
Views
Activity
Apr ’26
Reply to Xcode 26 fails to load SPM packages
@patrick Thanks for the post and providing a workaround, have you tried Xcode 26.5 beta without the workaround? Can you let me know if that works well for you? Anyone in this thread has filed a bug for this? If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Apr ’26
Reply to iOS 12.5.8 fails to bootstrap app
I'm seeing exactly the same crash, same source code, same Xcode version two weeks ago did not have the issue. I've pushed a new build 2 days ago and users with iOS 12 are getting a crash on launch.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’26
Unwanted Communication Reporting extension crash
I'm trying to implement Unwanted SMS and Calls reporting in an app I'm doing in my idle time. If I place a UITextField or UITextView inside a ILClassificationUIExtensionViewController, every time I select on such control the extension crashes without any logs. The closet idea I have on why it crashes it has something to do with iOS requesting the dictation feature. I'm using the latest (beta 8 at the time) iOS 16.0 beta on my iPhone 13 pro. Attaching my code here if you want to try for yourself: github
Replies
11
Boosts
0
Views
2.4k
Activity
Apr ’26
Apple watch Xcode pairing & connection issues
I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only
Replies
19
Boosts
0
Views
2.1k
Activity
Apr ’26
Reply to Apple watch Xcode pairing & connection issues
Let's just pile on here. Same issue. Unbearably bad and a productivity killer. Up to date OS on all devices. Spend half my day waiting for Xcode to reconnect to my watch that it was already connected to.
Replies
Boosts
Views
Activity
Apr ’26
Reply to Xcode now hangs; SDKs are "status unavailable"
I have the same issue with Xcode 26.4 after installing macOS 26.4. What help is (do it at your own risk, no guarantee): Force quit Xcode rm /Library/Developer/CoreSimulator/Images/images.plist Wait 1-2 minutes Launch Xcode You will be able to download the Platform Support Components from Xcode again.
Replies
Boosts
Views
Activity
Apr ’26