The Codex app seems to drop the connection if you click on anything (away, other parts of the app). The Codex CLI should hold onto a single connection for the entire session. I recommend giving the CLI another go. Although I do think Xcode could be a lot better here.

[quote='875002022, ryot, /thread/814587?answerId=875002022#875002022, /profile/ryot'] Unfortunately it seems like the reverse direction has some trouble, the Xcode 26.3 MCP is not working in OpenCode, there's errors stating that the output didn't match the declared schema. Would be nice to reference open Xcode tabs and selected text from inside OpenCode too - hopefully they fix this. [/quote] Yeah, I'm having the same problems trying to get OpenCode talking to the Xcode MCP tools. It looks like an OpenCode problem but it's a little hard to tell.

If you find a solution, please follow up. I've had a similar problem for nearly a year. Others have too (this is at least the fifth comment thread I've joined to observe). I've filed a feedback on the topic (FB16116052) but it didn't go anywhere. https://discussions.apple.com/thread/255888925 (my thread) https://discussions.apple.com/thread/255824865 (an older thread) https://developer.apple.com/forums/thread/775468 (a recent thread) It's all a bit of a pain.

I've had a similar problem for over a year. I've filed a feedback on the topic (FB16116052) but it didn't go anywhere. It's all a bit of a pain.

Similar problem for me. Although it's complaining about a different asset: The operation couldn’t be completed. (ModelCatalog.CatalogErrors.AssetErrors error 1.) Domain: ModelCatalog.CatalogErrors.AssetErrors Code: 1 User Info: { DVTErrorCreationDateKey = "2024-09-10 00:03:00 +0000"; } -- Failed to find asset: com.apple.fm.code.generate_small_v1.base - no asset Domain: ModelCatalog.CatalogErrors.AssetErrors Code: 1 -- System Information macOS Version 15.0 (Build 24A335) Xcode 16.0 (23050) (Build 16A242) Timestamp: 2024-09-10T10:03:00+10:00

I've filed FB13683931 with all my logs. As discussed in that Feedback, my problem seems simply to be that Xcode is "sticky" with its selection of interface. If Xcode sees my iPad over WiFi, first (the common case since WiFi is always on but cable is not always connected) it will establish debugging over WiFi. It will continue to use WiFi for debugging even if USB has subsequently connected and the devices list is no longer showing the WiFi "globe" icon. It never seems to switch unless forced. As a workaround for this problem, I can disable WiFi, start debugging (forcing Xcode onto USB) and subsequently re-enable WiFi. Due to the apparently sticky nature, Xcode will stay on USB for some time (when my computer next goes to sleep, all bets are off). As a followup, I should note: it's definitely not a network availability or routing issue. I can ping the iPad over the USB connection. And Xcode itself is discovering the USB connection (as indicated by it removing the "globe" icon). The problem is that Xcode isn't moving debugging over to USB unless forced.

I'm getting the same problem in Xcode 15 and Xcode 15.1 beta 1. All the poster extensions go crazy and you need to manually kill them or they burn CPU forever. There exists a GitHub project (https://github.com/biscuitehh/yeetd) that aims to simply kill them all in a loop: while true do pkill AegirPoster pkill InfographPoster pkill CollectionsPoster pkill ExtragalacticPoster pkill KaleidoscopePoster pkill EmojiPosterExtension pkill AmbientPhotoFramePosterProvider pkill PhotosPosterProvider pkill AvatarPosterExtension pkill GradientPosterExtension pkill MonogramPosterExtension pkill apsd sleep 5 done however installing a daemon to do this seems like overkill (pun?).

I'm having this same problem. Multiple rejections. Would love to know if there's a solution.