The identifier was com.apple.ios.StoreKitUIService I'm sorry to say that I don't remember how exactly I dumped this value out to the log. But that's the bundle-id for the app that asks the user to review the app.

Thanks, Ed. I created a brand new project, "DelaydLaunch", as you suggested. I see the same behavior. The app never installs on the simulator. In the Xcode status area, I see "Waiting to attach to DelayedLaunch on iPhone 16 Pro". I have created a ticket for this. FB16432171.

Gotta say, I greatly dislike the "don't do that" response. This has been a literal, old-school, x20 space character for decades. Why someone felt the need, now, to change the formatting... it seems rather arbitrary, and unnecessary. As was pointed out earlier, this is really just bothersome for unit tests. I have a number of tests which are checking output, and expecting only regular spaces in the output. Please help me understand why this change needed to happen.

To underscore the severity of this... We use CircleCI / Fastlane to build. We have local swift packages attached to our project. We simply cannot start using Xcode 14 because of this. While I can build on my own machine, Fastlane can't. And we can't upgrade all of our devs to this until Circle can build (and the rest of the devs can use the same Xcode). The concern here is that at some point, Apple will insist that submission to the App Store must be built with Xcode 14. Probably a few months away from that, but it is unsettling, nonetheless.

Xcode Cloud requires that your client be Xcode 13. Xcode 13 requires a minimum of "macOS Big Sur 11.3" It looks like macOS Big Sur runs on a 2014 iMac... but that is the oldest configuration, from what I can tell. So, while Xcode should run on that machine, newer versions of Xcode (like Xcode 14... whenever that ships in the fall) probably won't.

at the bottom of this page, it describes paths to the archives: https://developer.apple.com/documentation/xcode/environment-variable-reference Unfortunately, there doesn't appear to be any "post-archive" scripts you could run. (only post-build). If there were a way to do "post-archive" scripts, you could, theoretically, write a script to get the archive, zip it up, and send it off to another URL. Hmm. that's weird. I wonder why they give paths to archives, if you can't run a script after the archive process completes?

Same here.... after playing with Xcode Cloud last week, this morning I gave presentation about it to the group of engineers I work with, and encouraged them to play with it, and try it out... :facepalm: