xcode github

This sounds very similar to the issue discussed in https://developer.apple.com/forums/thread/700648. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

Any updates on this? We are facing the very same issue in our app and couldn't find a workaround for this. This issue is preventing us from migrating to Xcode 26. We have also filed the FB21327884 feedback in December.

Thanks for the post and it seems like when you moved to the new computer the git was not configured? The fact that you switched Macs and upgraded Xcode/macOS versions is a strong indicator, for me, that the issue stems from the environment differences or a configuration mismatch. Open your Terminal application and navigate to your project directory. What do you get when you request the git status? git status Does git status accurately reflect the staged changes you see in Xcode? Are there any untracked files that Xcode might be confused about? Are there any error messages? There are a few things you can do in the terminal to make sure git was installed and configured correctly: git commit -m Test commit message from terminal
 
git diff --cached
 
In Xcode, go to the Navigator pane (left-hand side). Select the Source Control tab (the icon with branches or waves). Does it show any errors or warnings related to your repository? Check the configuration on git with using the cor

[quote='874651022, mlgiPhone7plus, /thread/812911?answerId=874651022#874651022, /profile/mlgiPhone7plus'] I’ll include it in a reply for easier viewing. [/quote] Thanks. Generally, it’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. [quote='874651022, mlgiPhone7plus, /thread/812911?answerId=874651022#874651022, /profile/mlgiPhone7plus'] I was thinking about using screen time APIs [/quote] I’m not sure that’s viable. A key part of the Screen Time APIs is the Device Activity app extension. Swift Student Challenge expects you to submit an app playground (.swiftpm) and neither Swift Playground or Xcode will let you create an app playground that includes an embedded app extension. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi Michael, Thank you for your previous suggestion to use ViewAttachmentComponent for immersive controls. I've implemented it, However, I'm still facing two critical issues: Issue 1: Buttons in ViewAttachmentComponent Not Responding to Gaze + Pinch The buttons inside my ViewAttachmentComponent are visible and render correctly, but they do not respond to eye gaze + pinch gestures. This defeats the purpose of using visionOS's hands-free interaction model. My Implementation: ImmersiveView.swift (for panoramic images): struct ImmersiveView: View { @EnvironmentObject var model: AppModel @State private var menuEntity: Entity? @State private var isMenuVisible: Bool = true var body: some View { RealityView { content in // Invisible sphere for gesture detection let tapDetector = Entity() tapDetector.name = TapDetector tapDetector.components.set(CollisionComponent(shapes: [.generateSphere(radius: 900)])) tapDetector.components.set(InputTargetComponent()) content.add(tapDetector) // Create control menu using ViewAttachm

@DTS Engineer hello, I have same issue, below are details as you requested: Without NSExtensionPrincipalClass in Info.plist -> App Store Connect rejects upload with: Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found in extension Info.plist Screenshot of the extension's Info.plist Screenshot of the extension's Info.plist Screenshot of the main app's Info.plist With NSExtensionPrincipalClass -> Local install fails with: defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension Screenshot of the error encountered Screenshot of the extension's Info.plist Screenshot of the main app's Info.plist Environment: macOS Version 15.7.3 (Build 24G419) Xcode 26.0.1 (24229) (Build 17A400) iOS 26.2 Thanks you!

Hello, I think it's expected that Transaction.updates is not called (because when a user cancels its subscription, there is actually no new transaction to be pushed to the devices) but I expect Product.SubscriptionInfo.Status.updates to be called (also when a user changes plan from monthly to yearly for example, so we can be informed about the renewal product). This Status.update async sequence is called when I test with Xcode testing (with a configuration file). But this behaviour seems to be different in the Sandbox environment (or it's very very slow to update?). Before publishing the app, I want to be sure my flow is working but having two different behaviours between the Sandbox and the Xcode testing is not helping. Thank you, Axel

We're also getting the same error ... encountered an error (The test runner hung before establishing connection.) We tried nearly everything, including disabling the Thread Performance Checker in the test scheme shutting down all emulators via xcrun simctl shutdown all and erasing them xcrun simctl erase all force killing any potential hanging simulators beforehand clearing all Simulator logs and caches restarting the machine(s) But this still keeps popping up intermittently. We're using Xcode 26.2. Any tips on what we might want to try next? Thanks!

I have the same problem. Xcode 26.2, MacOS 26.2. This happens at least on every iOS 26 simulator (26.0, 26.1, 26.2). In my case I use the US-PC keyboard distribution in MacOS but simulator keeps using another one. I tried to restart them, create new ones, restart the Mac, Xcode... I started noticing it after changing to Xcode 26 from the 16 and resetting the simulator. Before resetting it everything worked well