In my case, the views were immediately popped when the pushing view had exactly 2 of the NavigationLinks. Not when it's just 1, or when its 3 or more. Mind-boggling. So now my code makes sure to add this meaningless NavigationLink when it would be 2 NavigationLinks without it.
iOS14.5.
Thanks for sharing the workaround!
iOSDevDaniel
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
From
Zagreb, Croatia
Post
Replies
Boosts
Views
Activity
You did the right thing passing the objectID to the other context, but probably didn't execute its fetch on the context's queue. Wrap that part of your code in backgroundContext.perform { ... } for async, or .performAndWait { ... } for sync execution.
You can opt to use your own identifiers instead of NSManagedObject.ID and this relieves you of so much hassle...
Hi @cconway, that is a completely different issue and you should file Feedback
Faced the same issue today. Workaround: create a new Widget Extension target and isolate your Live Activity Widget there