Posts

Post not yet marked as solved
8 Replies
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.
Post not yet marked as solved
26 Replies
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?).
Post not yet marked as solved
1 Replies
I'm having this same problem. Multiple rejections. Would love to know if there's a solution.