xcode github

No, you don't need an HTML page with the app-clip-bundle-id meta tag to fix URL invocation (Notes app or UIApplication.shared.open(url)) for TestFlight App Clips. This meta element is for production web/Safari invocations to trigger the card preview; TestFlight restricts dynamic URL taps/open calls despite green Domain Status and approved swcutil (Site/Fmwk Approval: approved). QR/Local Experience works because it bypasses these limits via explicit developer override. TestFlight Limitations Apple docs confirm TestFlight prioritizes controlled testing: Direct launch from TestFlight app (no card, loads clip). QR/NFC with Local Experience (full card flow). Arbitrary URLs (Notes, other apps) intentionally unsupported to mimic beta safety. Your AASA is perfect appclips entry + /numverify/appclip/* components match, CDN-propagated, swcutil validated. Your Options Method Works for Card+Launch? Setup TestFlight Invocations Partial (testers launch via TF UI) App Store Connect > TestFlight > Build > App Clips

Thank you for your reply. Our previous Team ID was H7837BUR8M. We tried changing the value of com.apple.developer.ubiquity-kvstore-identifier in the .entitlements file from $(TeamIdentifierPrefix)$(CFBundleIdentifier) to H7837BUR8M$(CFBundleIdentifier), but Xcode still reports the same error.

Hi @keckausome, please file a feedback report for Xcode Cloud (including your team ID and logs for this failure) and then post the feedback number here. You can file Xcode Cloud specific feedback using these steps.

If you transfer an app that uses iCloud key-value store (NSUbiquitousKeyValueStore), the transferred app should use the orignal store identifier, which by default is the bundle ID prefixed with the orignal team ID, so it still has the access to the existing data. The orginal store identifier is embedded in the new provisioning profiles you create for the transferred app. What you need is to update your entitlements plist with the full KVS value in your provisioning profile. This is documented in in the “Apps using iCloud” section here. In your case, is 57AWJ345M2 the new team ID? Using the new team ID as the prefix of the key-value store will lose the access to the orginal store. I believe that's why Xcode gives you the error. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello? #1 - I said I am not using XCode. Says so in the Subject. #2 - Your App Review Manager TOLD me voice in a webex meeting to post here in the forum to get an answer from an Apple Engineer! This is insane. You guys really seem to be struggling with this and providing a solution. I'm not using XCODE - I gave the exact situation above, I've been a developer for 35 years. My information above is enough for Apple engineer to give a solution.

watchOS 26.2.1 seems a worse pain than previous watchOS versions to copy cache over to Xcode 26.2 than before.

It sounds like you're aware of what a routing app is, but just to confirm details: A routing app provides navigational directions between two locations. It is enabled inside of an Xcode project by going to the Capabilities tab, and adding the Maps capability, which will then show you a list of checkboxes for the transportation modes by which you're able to provide navigational directions between points. Those checkboxes correspond to values added to your Info.plist file under a key named MKDirectionsApplicationSupportedModes. It sounds like you're not providing directions, but you should check to make sure the above capability isn't enabled accidentally. And if you're not providing directions, also don't enable this capability just to try and solve this error, as I've seen people get tangled up further by trying that. If all of that looks good and that capability wasn't accidentally enabled, then the next thing you should do is to open a bug report with the details of your App ID and the build number

Ok, so just to make things clear, is it expected that whenever I want to change the SpriteKit scene and also avoid concurrently accessing objects that may be changed in the current thread, I have to queue the SpriteKit changes by capturing all the needed state? It's just surprising to me that this is needed when SpriteKit is used as an overlay in SceneKit, but when running SpriteKit alone, it doesn't seem to be needed. I filed at least one feedback recently about crashes happening only when SpriteKit is used as SCNView.overlaySKScene. Is it expected that one has to use this... boilerplate code when embedded in SceneKit? Couldn't one do without it by simply overlaying a SkView on top of SCNView? class SceneController { private var shapeNode: SKShapeNode! func main() { let shapePath = CGPath(rect: CGRect(x: 0, y: 0, width: 10, height: 10), transform: nil) GameViewController.shared.updateSpriteKit { [shapeNode, shapePath] in shapeNode!.path = shapePath shapeNode!.fillColor = .systemRed } } } cl