Post not yet marked as solved
me too , simulators are pretty much unusable on my intel mac, i would submit a feedback, i did as well about the transparency issue.
i would give it a day or so, sometimes it takes them a little bit to the the symbols up. We usually go through this every release.
@phirk i have the same issue with cisco anyconnect. I actually had a 1 on 1 lab session with the xcode team during WWDC regarding this. They changed the stack from previous xcodes to a new stack called CoreDevice i belive. its mosty a network connection, so when cisco connects it 'kills' those devices and immediatly on cicsco disconnect it sees them again. Its a pain to have to disconnect to be able to debug on a device. i also submitted a feedback with as many details as possible about our cisco setup. They are looking into it, but it might not be a Apple thing. It could be Cisco Anyconnect and it also could be how its setup at your workplace. So as of right now its kinda an outstanding issue with no solution atm.
Post not yet marked as solved
also seeing this. thanks for submitting a feedback!
i know this might be kinda random, but ive run into this too, i can ONLY see my devices available for debugging if im not connected to my workplace VPN, as soon as i disconnect i see them. I have a FB submitted, seems kinda like a bug, but ill wait to see what they say.
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.
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
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
