xcode github

Same as yours. My Xcode Cloud reported this: Could not launch “SemantyTests (macOS)” Semanty encountered an error (Failed to install or launch the test runner. (Underlying Error: Could not launch “SemantyTests (macOS)”. Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. (Underlying Error: The operation couldn’t be completed. Launch failed. (Underlying Error: Launchd job spawn failed))))

Tag names are not available on iOS. Xcode does a pretty good job of explaining that. Consider this snippet: let values = try url.resourceValues(forKeys: [.tagNamesKey]) // ^ 'tagNamesKey' is unavailable in iOS let tags = values.tagNames ?? [] That fact is also reflected in the documentation for the tagNamesKey property. I’m not sure why the documentation for the tagNames property gets this wrong, but it’s definitely a bug in the docs and I encourage you to file it as such. Please post your bug number, just for the record Taking a step back, I can see why you might want to work with tags on iOS, so I encourage you to file a separate enhancement request asking for this property to be made available there. Again, please post your bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

hear add some debug code, MetalFX FrameInterpolator calling code like this: void MetalFXFrameInterpolator::MTLFXInterpolateFrame(const FrameInterpolatorRenderContextInternal& context, id frameInterpolator, id cmdBuffer) { id mtlTexOutput = context.idOutputTexture.IsValid() ? QueryMTLTexturePointer(context.idOutputTexture) : GetBackBufferColorMTLTexture(); id mtlTexPrevColor = QueryMTLTexturePointer(context.idPrevColorTexture); id mtlTexMotion = QueryMTLTexturePointer(context.idMotionTexture); id mtlTexColor = QueryMTLTexturePointer(context.idColorTexture); id mtlTexDepth = QueryMTLTexturePointer(context.idDepthTexture); id mtlTexUI = QueryMTLTexturePointer(context.idUiTexture); if (mtlTexColor.width != frameInterpolator.inputWidth || mtlTexColor.height != frameInterpolator.inputHeight || mtlTexPrevColor.width != frameInterpolator.inputWidth || mtlTexPrevColor.height != frameInterpolator.inputHeight || mtlTexOutput.width != frameInterpolator.outputWidth || mtlTexOutput.height != frameInte

Project Navigator file SCM status has been wonky from the first beta release of Xcode 26, and continues to be with version 26.2. It matches actual Git state perhaps 50% of the time, and needs a complete restart of Xcode to refresh. Someone needs to attend a refresher State Machines 101 course. It seems likely this situation affects all Git interactions in Xcode 26. Best option is using external client, cli or GUI.

Is there any progress on this? I am interested in this as a developer of long range peripheral devices to be used with an iOS app. I can't imagine LE Coded PHY aka BLE Long Range would still not be implemented by the time Bluetooth 6.0 rolls out? Granted, it was an optional feature of Bluetooth 5.x and is still only optional in 6.0 Also, as I understand from discussions elsewhere, an API for specifying PHY previously existed but was dropped (or went missing) a few iOS versions ago?

ENABLE_DEBUG_DYLIB is an Xcode-only build setting. It's something that controls how Xcode builds app bundles. It's not a compiler flag. You don't need it for Swift package manifests because app bundles are not defined in Package.swift manifests. Are you running into specific issues?

This is most likely a PhotoKit framework bug and not a problem in your code. The native picker works because it bypasses the same broken code path. Implement defensive timeouts and fallbacks to protect UX while waiting for Apple to fix it. Here are some workarounds you can try right away: Add timeout logic - Cancel stuck requests after 30s and retry or show error Use PHPickerViewController - Modern API that handles iCloud downloads more reliably Implement fallback - Try requestImage instead of requestImageDataAndOrientation if first attempt fails Pre-check assets - Use PHAssetResource to verify local availability before requesting If that does not help, please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem. Also, please include a sysdiagnose, reference threads 806349, 732820, 113692. Post the Feedback number here after you have filed a bug. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug

I'm experiencing the exact same crash in UIKit. With UIBarButtonItems and Popovers. On Mac Catalyst app build with Xcode 26.2 (17C52) on Tahoe 26.2. Same will happen with UIView as a source when presenting the a UIViewController if a zoom transition is set vc.preferredTransition = .zoom { _ in sendingView } Setting the info.plist UIDesignRequiresCompatibility to YES, prevents the default zoom transition and shows the popup with arrows.

Maybe consider opening a support request so one of our engineers can go through your Xcode settings with you. https://developer.apple.com/support/technical/

@Ja239 my subscriptions and business agreements are all approved If the status of your subscriptions is Approved in App Store Connect, review their availability in App Store Connect. Confirm you select all the countries or regions where you want to sell the In-App Purchases. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. Yet, when the paywall in my app appears, and someone clicks the subscribe button to pay, the IAP isn't appearing. It just loads forever. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. When I tested in Xcode it just kept saying products not found. Id's are the same, bundle id is the same, ive done everything. If your app fails to display its products when testing In-App Purchases in Xcode or the Apple sandbox environment, see TN3185: Troubleshooting In-App Purchases availability in Xcode and TN3186: Troubleshooting In-App Purchases availability in the sandbox, respec