a quick update (2023.01.20): as of this writing, 313 views on this, and no replies; we finally decided to burn a TSI on it ... DTS said, "We believe this issue is a bug. Please file a bug report ...", so we did, FB11958019. no workarounds, etc.., as yet. will try to post again if we discover anything.

update 2 (2023.01.25): DTS: "no code-level workaround at this time"; the feedback is still open

or, even better, have a preference to disable the colors entirely. they are ugly and distracting. also, have a pref to disable metadata by default. i don't want it (it's too small to actually see), and i don't want to have to turn it off every time.

i know this thread is supposedly about "beta 3", but i hope someone is still looking at it, because i don't see a newer one. i can't believe i haven't heard more people freaking out about this, and also that there seems to be no way to at the very least select side-by-side comparison. generally agree that the new system is a huge regression. nothing new to add really, except to be another small ignored voice crying out in the darkness: HEY APPLE, QUIT BREAKING SHIT.

the xcode support page states that xcode 15 supports sim versions from 14: hopefully, someone responsible for the development of xcode will wake up and actually provide this support sometime soon. ideally, i'm sure most developers want to adopt new technologies to gain the benefits thereof, but apple makes it difficult by not seeming to realize that in the real world, we have to also still support users on older devices. many of us don't have an extensive collection of old hardware laying around, nor the time to curate a stable of old devices running older os versions (which it is often impossible to downgrade to). for this reason, sim support is critical. i was looking forward to working with xcode 15, but so far, it's been mostly a disappointment, between this and the regressions in the commit screen ...

update 3 (2024.10.03): we're still seeing the issue periodically, so i went to check on my FB today, and found that it had completely disappeared with no notice and no way to search for it, so i created another, FB15365582

same here; april 2025 ...

(tried to post this as a comment on my last post, but couldn't get it to work ("your reply must include text in the body", whatever that's supposed to mean, after i just typed 300 chars)) ... anyway ... i guess if you think about it in a certain way, it makes sense: apple doesn’t know that, for example, we were only using those “apps” for testing; they have to assume that any app will possibly make it to app store distribution at some point. since apps need to remain available for download (by users who downloaded them before, even after removal), apple can’t allow the re-use of those bundle IDs for a different app. however, it would still be nice if there was a button somewhere to say "i'm never going to use this bundle ID for anything real, so let me actually remove it", which would then mark the ID for possible re-use if no app with that ID was ever live on the store (e.g., it was only ever used for testflight, which was why we ran into this problem when trying to transfer one of our apps to a different company ...)