“xcode github”

Please try this again with Xcode 26.4.1. Quoting the release note: Fixed crash for MetricKit apps built with Xcode 26.4 due to missing symbols when running on iOS, macOS, and visionOS versions below 26.4. Please rebuild your app with the updated Xcode to resolve the issue. (173827073) (FB22384135) Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

is this the way to get your first in-App purchase approved? If you still need to test your In-App Purchase, then there is no need to submit them for review yet. Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. TestFlight also uses the sandbox for In-App Purchases. Apple reviews your In-App Purchases in the same environment. However, if you are done with testing, submit your In-App Purchase for review. all works in Xcode. If you enable StoreKit Testing in Xcode, you likely tested your products in the local environment. To test in the sandbox, disable StoreKit Testing in Xcode, then follow the steps in Testing In-App Purchases with sandbox to test your products in the sandbox. Be sure to read TN3186: Troubleshooting In-App Purchases availability in the sandbox that identifies common configurations that make your In-App Purchases unavailable in the sandbox environment.

@amacia See TN3186: Troubleshooting In-App Purchases availability in the sandbox identifies common configurations that make your In-App Purchases unavailable in the sandbox environment. With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight....For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved? Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. TestFlight also uses the sandbox for In-App Purchases This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Is it documented that StoreKit may not return products duri

@selimce, @669miller , @Gascad , @slowfast , and @touchlinebet Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Same problem with non-renewable IAP. My review is rejected because of the IAP's were not seent in the sanbox environment. For us, it is seen in both xcode and testflight environments. Probably because of this bug in review view. Please follow these steps, then let me know about the outcome: Create a Sandbox Apple Account. On your testing device, sign into the above account. For more information, see Sign in to your Sandbox Apple Account for a development-signed app. Disable StoreKit Testing in Xcode in your Xcode

You are the man! Thnx Albert! Derive Mac Catalyst set to No was wat I needed. I'm running latest Xcode, so not sure what went wrong. And thank you for all the links! App is currently waiting for review. Reason for using catalyst was that it is an iOS first App, which happen to run great as a catalyst app on macOS without much tinkering.

This is with: macOS 26.4.1, Xcode 26.3, MacStudio-M1 There is the message after the crash/reboot Your computer restarted because of a problem - but the stack trace is beingn - not my driver, nor the kernel/dextloder, there is no log in Console, no crash report in Console.

Additional: It won't launch an app on my phone either. (No changes to the app, and it would launch in sim or phone before the failed update of Xcode.) It's just spinning in Launch phase of the build.

Thanks for the post and welcome to the community! This is something I saw long time ago when I was looking at how Mac Catalyst works and how the bundle id adds this prefix maccatalyst I think, but not positive as this is from memory. The issue you are running into may be caused by a conflict between how Mac Catalyst originally worked and how Apple handles bundle id registration today. When Mac Catalyst was first introduced Xcode automatically prepended maccatalyst. to your existing iOS bundle ID. However later changed allowing you to sell your iOS and Mac apps together under the exact same App Store Connect record. Do you have the latest Xcode release? Is it happening there? I would upgrade to the latest Xcode, however if not you need to tell Xcode to stop generating that maccatalyst. prefix so your Mac app shares the exact same bundle ID as your iOS app. Here is how to do that from this documentation: https://developer.apple.com/documentation/uikit/mac-catalyst https://dev

Thanks for the post. I believe still the short answer is that you do not need a paid Apple Developer Program membership, but you do need a free Apple ID, which Xcode refers to as a Personal Team. Is that still the terminology? As the free account allows you to: https://developer.apple.com/get-started/ Access beta versions of Xcode and operating systems
 Test your apps directly on your own devices using Xcode
 Engage on the Apple Developer Forums
Submit bugs with Feedback Assistant 
Participate in online Meet with Apple events Apple requires all apps installed on a physical device to be signed. This ensures the device knows exactly who built the app and prevents malicious software from being installed silently. To do this, Xcode needs an identity to sign the app with, which it calls a Team. You can use your standard, everyday Apple ID to create this team for free. Xcode will now automatically generate the free provisioning profiles and certificates needed to install

@setoelkahfi Please try Xcode 26.5 beta 2 as there is a fix for that issue ttps://developer.apple.com/documentation/xcode-release-notes/xcode-26_5-release-notes Albert
  Worldwide Developer Relations.

[quote='884572022, kpatel1991, /thread/821961?answerId=884572022#884572022, /profile/kpatel1991'] the ShareableCredential one appears but even if we check it - Xcode still isn't allowing us to deploy. [/quote] Right. That is the nature of the bug in question here (FB22439399). You need to apply for the Contactless Pass Provisioning (deprecated) capability. There’s no form to do that specifically, so use the common Contactless Pass Provisioning capability form. [quote='884560022, Nagavendra, /thread/821961?answerId=884560022#884560022, /profile/Nagavendra'] It’s working now with the following approach … [/quote] Excellent news. [quote='884560022, Nagavendra, /thread/821961?answerId=884560022#884560022, /profile/Nagavendra'] However, this does not seem like a proper or permanent solution. [/quote] Indeed. The permanent solution will involve a fix to Xcode, which is what we’re tracking with the above-mentioned bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let