i dont think Appstore connect is quite ready for iOS17 uploads quite yet, they usually announce when it can receive them, i would wait until we get official word then try again.

same issue here, on xcode15 simulators, makes it almost impossible to test on simulator, has anyone filed a FB? im going to

Yes they will, usually by early the next year in the .3 - . 4 release they will drop support for Monterrey, been pretty standard in the past years

i have the same issue i filed a feedback, but you should also file a feedback, im not too concerned about breaking constraints especially with apple provided api's and it still shows correctly / no ui glitches, but they should be reported

take a look at this twitter post from a xcode engineer seems to be a big issue with storyboards / nibs in 13.4.1 after installing 14 beta, but they give a workaround. see if this helps: https://twitter.com/AnaCalinov/status/1545118596820439040

take a peek at this twitter thread from an xcode engineer, They seem to be aware of xcode14b3 having big issues with xcode13.4.x and below. Looks like they have a workaround , as they made a back end change for now. but you have to open a certain pane in xcode 14 then you can go back to xcode 13.4.1 etc. https://twitter.com/AnaCalinov/status/1545118596820439040

take a peek at this twitter thread from an xcode engineer, They seem to be aware of xcode14b3 having big issues with xcode13.4.x and below. Looks like they have a workaround , as they made a back end change for now. but you have to open a certain pane in xcode 14 then you can go back to xcode 13.4.1 etc. https://twitter.com/AnaCalinov/status/1545118596820439040

i plan to keep using watchkit for my watchos app, until they force min release of 7 (maybe in a few years, apple really hasnt moved the min target of watchos that much) then i will probably just drop support. No sense of trying to rewrite everything that doesnt get used to justify it anyways. Kinda stinks, but apple calls the shots. I noticed even before Beta 3, if you created a new watchkit app, there was no option for storyboard, only swiftui, so not too surprising here, now they have a deprecation warning to kinda go hand in hand with that. so to your points my opinion: Your app will continue to work just fine, even if you have a watchos target greater than 7.0. I dont see apple simply just removing watchkit support for watchos anytime soon, possibly never. Just new apps will have to be done in swiftui. thats a good question, probably their desire to promote swiftui as much as possible I dont believe so, i think deprecation is a strong word here, but going forward they want new apps (and maybe in some fantasy dreamland) existing apps to use swiftui.

It seems if you download and install xcode 13.2.1 it WILL work, but still 13.4.1 will still not work :( . so as a workaround install 13.2.1 Apple any thoughts i would love to have 13.4.1 working again? :) https://twitter.com/parrots/status/1544817250410037248

same with me i cant even build my project anymore in xocde13, keep getting Encountered an error communicating with IBAgent-iOS, i tried removing xcode 14 but still am getting the error, tried rebooting etc.

in the Whats new in UIKIt video : https://developer.apple.com/videos/play/wwdc2022/10068/ they mention UIDevice orientation has gone away. Instead they say use : https://developer.apple.com/documentation/uikit/uiviewcontroller/1621438-preferredinterfaceorientationfor

I attached a sample project, clean xcode 13 ios app, added watch target, then opened up xcode 14 did the migration and doesnt run on ios simulator (seems to run on device though) so maybe its a simulator issue / check? FB10066285

This worked to get it to build, i needed to hand add an extension delegate and the corresponding main / infoplist entries. but now when trying to run on a iphone simulator it says this. Feel as if im missing something else. Please try again later. Found WatchKit 2.0 app at /Users/x/Library/xxxxxxDeveloper/CoreSimulator/Devices/E18868EE-130C-4159-AAF2-95319072DD5E/data/Library/Caches/com.apple.mobile.installd.staging/temp.JH6Xuf/extracted/Payload/TestingApp.app/Watch/TesterExt.app but it does not have a WKWatchKitApp or WKApplication key set to true in its Info.plist

i notice this on many apps on my ipad (on ios15) apps that i know should have a Light Status bar color are sometimes dark, but if you leave and come back its "correct" i have a feeling this is more of a system bug, than a coding one. As its happening on many apps I would report it.

FWIW , i made a post waaaay back in the beta 3 days (that's when it started to happen) with the same exact issue (appleaccountid) https://developer.apple.com/forums/thread/685202 i would submit a feedback (i did) the more that submit one the more attention it will get.