Apple Maps Guides

The most crucial step! Enable Wireless Debugging on your Apple TV. On Apple TV: Go to Settings → Remotes and Devices → Remote Apps and Devices Keep this interface open. Your Apple TV will automatically enter Waiting to Pair mode. (A message will appear on screen: Ready to connect using Xcode or Apple Configurator) Do not exit this screen! Otherwise, Xcode won't be able to detect the device.

@jhowlin Make sure you file a bug report using Feedback Assistant. Apple needs to know that more than one person is having this issue.

【Apple TV 4K (3rd generation)】 If you have a physical Apple TV, please follow these steps: Connect the device Open Xcode → Window → Devices and Simulators Ensure your Apple TV and Mac are on the same Wi-Fi network Click the + at the bottom left → Pair Apple TV Enter the pairing code displayed on your Apple TV as prompted Once completed, your Apple TV will appear in Xcode's device list Re-enable Xcode signing Select your tvOS target Open Signing & Capabilities Check Automatically manage signing Select your Team (developer account) Xcode will automatically: Register com.********.tv with Apple Create a tvOS Development Provisioning Profile Bind it to the Apple TV you just connected Issue resolved – Xcode will no longer report errors.

Thanks for the reply @DTS Engineer. For my project, using Swift is not really an option for now. My stack is more C++/Objective-C based, and so gRPC-Swift and SwiftNIO are not ideal. From what I gathered, there isn't an equivalent or other alternative that would enable this for Objective-C. There is grpc-ios, but, without going into details, it doesn't really make sense to use that either, I'm looking for a lower level framework. I see two options for me: Use the Network framework and take care of the whole TLS handshakes, HTTP headers, etc and obtain my trailer support that way. Use libcurl, which would do a lot of that for me and get trailers from there, as it supports it. Option #1 is a huge lift and would mean a lot of maintainability problems in the future. Option #2 is a bit safer, but I'm afraid of it contradicting your statement: make sure to use Network framework as your underlying transport, because that ensures that your app will do all the usual things expected on Apple platforms. Does th

I figured it out! When Xcode performs Automatic Signing, it: Communicates with the Apple Developer Center; Searches for registered devices under the account; Automatically generates or updates the corresponding Provisioning Profile. If there is no Apple TV (tvOS device) in the account, Xcode will fail because: Apple requires that development profiles must be bound to at least one physical device.

@DTS Engineer creating an empty project and copy/pasting the assets catalog does indeed reproduce the issue, the problem is that such catalog contains over 3k files total and its size is around 1.2GB, I don't think one can attach samples that large. Of course in that 1.2GB there are assets that do not contribute to the issue, and I'm trying to slowly find a minimal set of assets that causes the issue to appear. Apple Support seems to require at most 50MB which is basically impossible for the scope of the project. The issue appears with every version of XCode, it just fails with this error when building with Archive scheme, but runs and builds fine if a simulator or physical device is selected.

Inspired by this thread I bumped WWDC 2025 Session 299 Deliver age-appropriate experiences in your app to the front of the EskimoTV queue, and that made it clear that .invalidRequest indicates a programming error. Start here in the video. I encourage you to file a bug against the docs to make this clearer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

In my case it pauses at Copying shared cache symbols from Apple Watch (13% completed) Xcode will continue when the operation completes. and then Apple Watch may need to be unlocked to recover from previously reported preparation errors Ensure the device is unlocked and near this Mac for better connection quality. I removed passcode from the watch, put in on my wrist and kept tapping the screen to keep it always on, to no avail. What a joke Apple has become!