Submitted FB15595530 as I have the same issue. It would be super helpful if this worked on List.

Filed as FB15008170

Still present in iOS 18 beta 8.

I am experiencing this issue, although only when NavigationLinks at tapped after a list has been filtered using .searchable. That is, rows containing a NavigationLink that normally will only lead to one push on the stack will modify the path twice when that row is tapped after filtering the list with a search term using a .searchable search box. This remains present in both iOS 18 beta 7 and in iOS 18.1 beta 2.

Yes, I'll put together a test project and try to reproduce the issue.

This is a fascinating lead I have not previously found: https://stackoverflow.com/a/42751426/842106 I wonder whether my custom NSManagedObject subclasses in Swift are somehow to blame, causing unwanted bridging to Swift types, or whether I need to annotate the @FetchRequest in some way to prevent this happening...

Do not be as dim witted as me! com.apple.developer.icloud-container-environment must be set in your .entitlements file, not your app's info.plist file! Additionally, if you have separate .entitlements files for your debug and release builds, be sure to set this value in the debug one. Note that TestFlight builds and releases in the store are unaffected by this entitlement—they will always use the production environment regardless of whether this entitlement is set and regardless of what it is set to if it is set.

I have the same issue. FB9807975. MacBook Pro 2019 16" i9. Am yet to upgrade to Monterey 12.1, so trying that now in case it resolves this although from what I'm reading elsewhere, doesn't seem to.

An addendum. The two use cases outlined above are: to be able to return entities of any of the types that have properties that meet a particular search term, and to display the other entities that are in relationship with a selected entity. In the latter case, one particular thing I want to do is to present a chronological timeline of the entity relationships to other entities that have been added or changed over time, e.g., this customer is now in a relationship with this business, or with this product, as a single unified timeline. What I'm starting to think is that the way to do this is perhaps to create an intermediate entity of some kind, e.g., a timelineEvent entity, which is created at the point of creating a relationship between two of my existing entities. These lightweight entities would not be used to manage the relationship between the entities, but would be used to provide a history about those events. Thus, displaying a timeline of those events could be via an NSFetchedResultsController that is fetching only a single entity type, timelineEvent, and then from that creating one of a range of collection view items depending on the type of entity the relationship was with. Is this a good approach to the problem I'm outlining? In other cases, it likely makes sense for my use case to just continue to fetch each of the entities via the relationship, on a per-entity-type basis, and then display those as individual collections of entities, rather than trying to intermix them. But I am most interested in any feedback or suggestions. :)