Oh now I see why I didn’t have any luck with DeviceActivity framework until now. That’s sad, would be very cool and useful to have it work withou family stuff too. I can imagine many usecases. Hopefully they’ll change their mind.

update: I now filed a feedback for it FB9211136

Ok I guess it was actually partially my fault. I see they fixed some navigation issues in beta 3. but if you have multiple levels of navigation you have to set isDetailLink(false) accordingly. in my example I have a main list going to another view (let’s say View A). And from this view you can go to a detail view. Now if I dismiss from detail view i want to go back to view A and not the main list. so i have to set on the links in the main list isDetailLink(false)

I have the same issue. Didn’t happen on iOS 15. i haven’t found a workaround so far sadly.

Ok I just accidentally found a workaround, use with caution because I haven't checked yet what exactly it does (but it removes the additional back button). Adding .toolbarRole(.automatic) to the content view fixes it (or any of those roles). DocumentGroup(newDocument: TestDocAppDocument()) { file in             ContentView(document: file.$document)                 .toolbarRole(.automatic) }

I still see problems regarding saving Documents even in iOS 16 with FileDocument. i understand that FileDocument is when you use structs and it detects changes and should save. But it doesn’t seem too reliable. i just wish i could trigger/force save. any solutions?