“DTiPhoneSimulatorErrorDomain Code 2”

What is the current status of this issue? In the Xcode/iOS 26.4.1 SDK, attempting to use Metal 4 symbols still causes an error. The code below works when targeting iOS Device, Designed for iPad, or mac, but for the Simulator, I get the error: “Cannot find protocol declaration for ‘MTL4CommandQueue’; did you mean ‘MTLCommandQueue’?” #import #import @interface MyClass : NSObject @end @implementation MyClass - (void)test { id queue; } @end

Hi, we are seeing this exact same issue with iOS 26.4.2 + the current iOS 26.5 beta version. We can not update our App anymore having the VPN tunnel running! Removing the VPN Profile instantly resolves the issue.(which isn't a solution) installcoordinationd: Failed to acquire termination assertion RBSRequestErrorDomain Code=5 Error acquiring hold on plugins PlugInKit Code=14 plugins are busy busyPlugInUUIDs = ******.NetworkExtension Same build is perfectly updating on e.g iOS 17.* or IOS 18.* devices.

Hi Quinn and Kevin, To the feedback FB22691771 I now added: A small example app found online, with the same setup as our app. Two sysdiagnoses, one from the sender end (the app initiaiting pairing) and one from the receiver end (the one accepting the invitation). As requested, the pairing attempts should be visible within the last 2-3 minutes in the sysdiagnose, pairing attempts were performed until pairing succeeded. Additionally I attached a side by side screen (time matched) recording showing both views (test setup). On the bottom right it would be the receivers view. Additionally, the video was recorded during the same period as the sysdiagnose. So timestamps (at least minutes) should match. And again for this to be reproducible: Turn Wifi on + don't be connected to any access point (on both devices). Be on iOS 26 on both devices (on iOS18 this is NOT reproducible) I would add the attachments here as well, but file size and formats are limited. Thank you for your help!

[quote='824713021, Sangeetha_G, /thread/824713, /profile/Sangeetha_G'] 1- Once we establish data path, Why iphone initiates data path termination instead using the same service for data path exchange. [/quote] Are you seeing this with the latest versions of iOS? So iOS 26.4.2 or the iOS 26.5 beta? The reason I ask is that the behaviour you’re seeing looks like an issue we fixed in iOS 26.4 where, after doing a pair setup, we would establish and then tear down a datapath. Given that you’re testing on iOS 26.2, it’s likely that this is the cause of the results you’re seeing. [quote='824713021, Sangeetha_G, /thread/824713, /profile/Sangeetha_G'] 2- Why do we go for PAIRING VERIFICATION everytime. [/quote] I believe that’s required by the Wi-Fi Aware spec. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m going to tackle a few of your issues now, and we can come back to the others once we’ve driven these to a conclusion. [quote='886912022, matteoq, /thread/821250?answerId=886912022#886912022, /profile/matteoq'] Glitch after successful login … is there any sort of known workaround/solution to this? [/quote] Not that I’ve seen. However, if you can reproduce this reliably then I encourage you to file your own bug with the details. Part of the issue with getting traction on FB12074874 is that it only reproduces in odd situations, at least IME. Please post your bug number, just for the record. [quote='886912022, matteoq, /thread/821250?answerId=886912022#886912022, /profile/matteoq'] Plugin update [/quote] It depends on the exact sequencing. When you’re at the login window, the system has already loaded your plug-in so updating it on disk doesn’t help. I typically update my plug-in when I’m logged in and then log out. The system will then pick up the new plug-in as part of bringing up loginwindow for the new se

Earlier I wrote: [quote='884707022, DTS Engineer, /thread/821961?answerId=884707022#884707022'] The permanent solution will involve a fix to Xcode [/quote] which was a bit simplistic. There are actually three factors involved here: The capabilities assign to your team The Xcode version The Developer website The second two have recently been updated, and it’s possible that that’s sufficient to resolve this issue. If you try the obvious path forward with the latest Xcode 26.5 beta, do you still have problems? If you don’t, then you’re all set. If you do, then my advice from earlier stands. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='887385022, greggwon, /thread/825449?answerId=887385022#887385022, /profile/greggwon'] And again, this is Mac (Designed for iPad) build [/quote] Ah, yeah, I got mixed up with the terminology. A “Mac (Designed for iPad)” build takes you down the iOS apps on Mac path, which is definitely not Mac Catalyst. Sorry about the confusion. iOS apps on Mac should follow iOS conventions, so: There’s no hardened runtime or App Sandbox, so no need for com.apple.security.device.audio-input or com.apple.security.device.microphone. You do still need NSMicrophoneUsageDescription. With that in mind, I sat down to try this out. Here’s what I did: Using Xcode 26.4 on macOS 26.4.1, I created a new test project. I wired up two buttons to some basic recording code (see below). In the Info tab of the target settings, I added a NSMicrophoneUsageDescription property. I ran the app on my iPhone. I tapped the Start button. iOS presented the microphone permission prompt. I tapped Allow. I spoke some words. I tappe

Here is a code snippet that lets you tap 2 points on the map to calculate a route and verify that MapPolyline is still rendered below the traffic layer in certain cities, despite using .mapOverlayLevel(level: .aboveRoads). Try highways import SwiftUI import MapKit struct ContentView: View { @State private var position: MapCameraPosition = .region(MKCoordinateRegion( center: CLLocationCoordinate2D(latitude: 51.5, longitude: -0.1), latitudinalMeters: 2000, longitudinalMeters: 2000 )) @State private var tappedCoordinates: [CLLocationCoordinate2D] = [] @State private var routePolyline: MKPolyline? = nil @State private var isCalculating = false var body: some View { ZStack(alignment: .bottom) { MapReader { proxy in Map(position: $position) { if let polyline = routePolyline { MapPolyline(polyline) .stroke(.blue, lineWidth: 10) .mapOverlayLevel(level: .aboveRoads) } ForEach(tappedCoordinates.indices, id: .self) { i in Marker((i + 1), coordinate: tappedCoordinates[i]) .tint(i == 0 ? .green : .red) }

Hello everyone, I’m looking for some guidance and, if possible, assistance with an issue I’m experiencing. I’ve been using Codex with Xcode since the beginning of my project, and I used to be able to use both the Codex agent and ChatGPT through my ChatGPT login. I have a paid Pro account. However, two days ago, my Codex agent was signed out, and I lost access to Intelligence features and the ability to send prompts. I can no longer sign in to my Codex agent in Xcode—the only option available now seems to be using an API key. I tried that workaround for a day, but I quickly hit my API usage limit. Has anyone else run into this issue? If so, how did you resolve it? I’ve already tried deleting Xcode and all related files and logs, then reinstalling, but that didn’t fix the problem. Thank you.

We are seeing what looks like the same issue with our TestFlight watchOS app. In our case the watch app is paired with an iOS app and was installed from TestFlight. The watch app launched successfully earlier on the same device and same installed build, including from a complication, and successfully recorded/transferred data. Later, tapping the app icon or complication did nothing. We reproduced the failure from the Mac with devicectl device process launch and got: The application failed to launch. (com.apple.dt.CoreDeviceError error 10002) BundleIdentifier = FBSOpenApplicationServiceErrorDomain error 1: RequestDenied FBSOpenApplicationErrorDomain error 3: Security Unable to launch because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. A few details that may be useful: The same TestFlight build had launched successfully earlier on the same watch. The app was still listed as installed by CoreDevice. The companion dev/watch build c