There's even a Reddit post - https://www.reddit.com/r/iOSProgramming/comments/1c5pddy/wwdc_video_deleted_background_execution/ - asking about where to find this video

I am not seeing the same results as Xcode 15. Instead I get a package icon without a ">" caret to expand to see the files. Any other suggestions? Issue turned out to be that I had the package opened in a separate Xcode window. Once I closed that window, I was able to browse the files.

I opened Feedback Assistant Issue FB12576800 over 6 months ago with no response. I opened a TSI via Apple DTS and only got the response that the issue is known and is being worked on, but nothing more since the past summer.

I ran into this problem in May 2023, and opened a Feedback Assistant Ticket (FB12576800) in July 2023. I just checked yesterday and still no updates from Apple. I reached out last summer via a TSI to Apple DTS and got a minimal response that "the team knows about the issue and is working on it". I hope it gets fixed someday...

Ah, I wasn't aware of the getpass option! This is a script, so I will give that a shot and see if I can script it up from there.

Sorry for the delayed response, I didn't see your feedback until today. I can run the xcodebuild archive command (wrapped in a Makefile) from the terminal window in a screen share session with no problem, but no prompts for password. If I run the same command via SSH, I get the same error I posted before. If I run security unlock-keychain in the SSH session and then re-run the archive command, it works. What I can't figure out now is how to effectively have CI run the same keychain unlocking when the job is run as a GitHub Action workflow given that the security unlock-keychain is interactive on the command line. Is there any way to do the unlock programmatically without having to hard code the password for the account to unlock the keychain?

Thanks for your interest here, Quinn. Our interest lies in the fact that we have a third-party dependency that generates code for specific platforms. Up until recently that dependency was only building for x86_64 simulators alongside arm64 devices. With their recent update, they now produce an xcframework, which includes the simulator binaries for the platform on which it was built. They don't have an easy way (yet) to cross-complie and include both simulator platforms (x86_64 and arm64 iphonesimulator) alongside the arm64 iphoneos binary. We could invest in figuring this out, but with the signaling from Apple that Intel machines will disappear it is less than ideal investment of our time to figure it out. At the moment we can use Xcode Cloud for archiving and submitting builds to TestFlight and the App Store, but not for running our unit test CI process for every pull request. We were hoping to move off our self-hosted GitHub Action runner to use Xcode Cloud exclusively, but until we can figure out the architecture issues for the simulator, we are stuck since our development machines are Apple Silicon.

I too am interested in knowing if/when the transition from Intel to Apple Silicon would be planned for Xcode Cloud.

Just checking in to see if you ever figured this out? We're in a similar boat and would love to solve the problem as well.

I tried what @freightmike suggested, but when launching the resulting copy, I get an error that the app is damaged and can't be opened because the file was downloaded on an unknown date. It wants me to trash it, but can't even trash it for me and instead requires me to manually delete it. If you have overcome this, I'm all ears. Otherwise, I'm going to have to take @davfre's approach and use a 3rd party terminal to support both native and Rosetta mode terminals.

I am seeing this with Xcode 14 as well, and accepting the upgrade reports no changes necessary, but it doesn't dismiss the warning 😩

I can confirm that Rosetta is not a cure-all here, as we have some dependencies that require us to run in Rosetta mode all the time and we still suffer from this issue.

I'm having the same issue, following this thread if anyone has any ideas.

I am seeing the same issue for our iOS project with a 3rd party Swift Package. I can build and archive in Xcode from the GUI, but xcodebuild fails with 482 errors, and at least the last few are the same "error: no such module" error. Looking forward to anyone else weighing in here with any suggestions!