Post not yet marked as solved
Does this project happen to use EXCLUDED_ARCHS=x64_64 on any targets? If so, that launch failure might indicate a bug that was discovered with Xcode version 15.2 and 15.3. Otherwise, if you could generate the full preview diagnostics and file a Feedback Request, we can take a look at the full diagnostics. You could also look for any crash reports in ~/Library/Logs/DiagnosticReports for you app as a starting point (our full diagnostics would contain these if they exist).
Post not yet marked as solved
Thanks for the bug report, we'll take a look. Just to clear up one thing: the warning about missing CoreAudioTypes is benign. The real failure is later with missing symbols. This might be a known issue or it might be a new instance of a previously fixed issue. Either way, we'll dig into it.
This was a UI change made in Xcode 14. Previews in Xcode are now live by default, and one preview at time allows you seamlessly move between previews while keeping them fully interactive.
Post not yet marked as solved
We'd need to see the code to see what could be going on. It could be that you're previewing your view directly, so it can go edge to edge. But when you run your app, it's in a container that has a constrained size.
Post not yet marked as solved
If you need to stay on those versions you could also try reinstalling Xcode. It looks like possible the code signature of one of the simulator runtimes is invalid.
This is a known issue, please file a bug if you have a specific use case in mind though!
Post not yet marked as solved
Previews intentionally pause when you hit Command-B to avoid builds for previews accidentally stomping on builds for running. When the preview pauses you should be able to hit the refresh button in the preview area to restart the preview, or use the key combo Command-Option-P.
Post not yet marked as solved
Two things to try:
Double check the Info.plist in your DerivedData for the app you're building. Is there a key for the bundle identifier? If so, what is the value?
Otherwise, this sounds like your Xcode install might be invalid. I know this is a lot of work, but could you try deleting and re-installing Xcode?
Post not yet marked as solved
This sounds like a bug we'll want to look at. Can you please file a Feedback Report and include as much information as you can (build log, ideally the asset catalogs in your project, etc). Thank you!
Post not yet marked as solved
No there is not currently a way to do this, but please do file a bug because we'd love to hear more about your use case!
Post not yet marked as solved
No there is not currently a great way to do this.
You could try adding two new packages:
A package containing your development code and assets only
A package with dependencies on your new development assets package and your original package
For your debug build, build this new root package from #2. And for the release build, build just the original package.
You can even add your preview providers to package #1, pin the preview, and then continue editing in the original package to get all the benefits of previews, but still putting preview providers and such in the other package.
And if you only have development code (and not assets), you could always just surround that code with #if DEBUG
No there is not currently a way to pick the image or a description. Please file a bug, we'd love to hear your use case!
Post not yet marked as solved
When it jumps back to your applications' root view controller, is the preview interact-able at that point? If not, then the preview is showing a snapshot of the content when it first came up, and likely the app has crashed.
It would help us to take a look at the diagnostics when this happens. When you reproduce the problem in Xcode:
Either (a) an error banner will appear, click the "Diagnostics" button in that banner. Or (b) if you’re not seeing an error but you still want to provide diagnostics, you can get the same diagnostics window by going under the Editor menu in the menu bar, then selecting the Canvas submenu, then selecting “Diagnostics”.
In the sheet that appears, click "Generate Report" in the bottom left of the sheet
Attach (or make from the folder) the resulting zip file to the bug (will be named something like previews-diagnostics-0123456789.zip)
Post not yet marked as solved
View bounds should be showing if you check "Show View Bounds", but there are some things to keep in mind:
Previews will only show view bounds for views created in the file you're viewing, even if the preview is showing views across files
There are some known issues with view bounds when views are located inside of certain container views. If you file a bug and attach your project we can diagnose if you're hitting one of these cases.
Post not yet marked as solved
I believe this is a known issue, and unfortunately we don't have a workaround at the moment.
