Dear Apple, please archive the wwdc23 slack Q&A for the time when the resource goes offline. There's tons of questions and answers that don't exist anywhere else or are extremely hard to find. E.g. answer to SPM checkouts folder: Question: Dear SwiftPM team, Is there any way to keep SPM checkouts outside of project's DerivedData folder? Since it is kept there, whenever DerivedData gets removed, packages need to re-fetch. Answer: Xcode looks at the IDEClonedSourcePackagesDirPathOverride user default in the com.apple.dt.Xcode defaults domain, and if it's set, the checkouts will be placed in that directory instead.

The INUpcomingMediaManager has only couple simple functions. But how are we supposed to test what it does or if what were doing is correct? Where are the things from setSuggestedMediaIntents supposed to be found?

The documentation notes that Xcode Cloud supports self hosted source control options and how to connect to one. However in an enterprise environment these are often accessible only through the internal network. Is that something Xcode Cloud supports or is it only for source controls accessible publicly? If it's supported is there documentation how to configure that?

Will Xcode Cloud report the build status' back to the source control provider? Will it be possible to get any other build results to e.g. Github? Having everything integrated into Xcode is great, but it's often beneficial to have the status or other information outside. E.g. if the source control is set up in a way that it allows merging the pull requests only after there is a passing build or when the code coverage passes certain threshold.

It seems that the archive shows the artifacts produced by the Xcode build process. Will it be possible to upload any custom artifacts e.g. something produced by a code analysis tool, and will they be visible in the build results?

Hi, is there any other way to run simctl commands before UITests, besides using the "Pre-actions" script? I.e. is it possible to run the commands between the tests to reset states? The resetAuthorizationStatusForResource: was a great addition, but it would also be nice to reset other things, like keychain or deleting the app, which are not available in the API, but exist in the simctl.

So the sandbox servers can't verify the receipt generated by the StoreKit testing. Is that something that might change in the near future? I'm failing to see the point of doing client side verification or skipping the verification completely, if there's already server set up for the task. I would also imagine that people would like to test the whole system, not just how the app UI reacts to the state changes.