Thank you for your post, two years ago. I'm using iOS 18.0 on Xcode 16.4, with NavigationSplitView in the initial List View. On a smaller iPhone the initial view is the [detail:] view. It seems to work fine, but After a while the device view freezes. When using Instruments there are a few problems with Core Animation Commits and Time Profiler limits that a crossed. It looks like NavigationSplitView is still not supported on smaller (SE) iPhones. Two years, and I have the same issue, wow something is broken here. Should I be using something in the initial list view?

Deleted all Projects from the DerivedData folder Cleaned the Build Folder Quit Xcode re-Opened Xcode Performed a Run Got the "Unable to Install" Message again Issued a report to Apple Closed the Project Created a new Project Performed a Run The Message appeared again for the new Project?

Thanks for the Workaround. Count me in with Xcode Version 16.0. Could not find another article on this subject. What is the Best Practice to help get this fixed with Apple Computer.

Current iPad (7th generation) used a month ago, has iPadOS Version 17.1.1. The condition originally described not longer exists. The right pane detail view is updating when the left pane has a new selection. Thank you for your follow up.

Receiving the same warning with: import SwiftData @MainActor class…: ObservableObject { @Environment(\.modelContext) private var modelContext init() { let descriptor = FetchDescriptor<Location>(predicate: #Predicate {$0.areaName != ""}) let count = (try? modelContext.fetchCount(descriptor)) ?? 0 <<== Warning here }} Then the App Crashes Not interested in a View with a List Just a [fetchCount]

I'm using Xcode 14.0, have we gone back to Xcode 1.0? Why, is this time saving feature missing in action? Which Apple Team came up with this dark idea? Is there something broken here? Removing this feature makes troubleshooting a Core Data Model a lot more time consuming and less reliable! Over the last 4 months there has been NO reply from Apple, is there anyone from Apple listening to so many developers on this issue? What a BAD practice!

On 9/13/22 updated to Xcode 14.0, but iOS 16.0 is not available. Now: "This operation can fail if the version of the OS on the device is incompatible with the installed version of Xcode. You may also need to restart your Mac and device in order to correctly detect compatibility". Am I missing something here? Do we need to wait for iOS 16.0 to develop for iOS 15.7, which is the current highest iOS device version?

This happened again weeks later. Using Menu > Source Control > Discard All Changes… and the Build is Successful again. If you are having the same problem, please leave a Comment

Can SwiftUI AsyncImage use Images saved as a File on an iCloudDrive?

Today the condition is April 12, 2022, macOS 12.3.1, Xcode 13.3.1 just installed and Swift 5.6.1. Is there a work around for this? I have been working on this for a few days, why is this problem NOT fixed by now? My "User Experience" is not very good, for whoever cares.

This is in addition to my comment two days age. After doing a little more troubleshooting I found this information. Hope this helps to isolate the root cause.

I also have the "Could not read serialized diagnostics file: error("Invalid diagnostics signature")" warning. I've tried a few improvements with restarting Project after deleting it's "xcuserdata". Thank you for posting this Question, hope it gets resolved as soon as possible. I WILL be back frequently on the status of the Question. It's on my Calendar. How many other Developers have the same situation?