The issue was one of the ViewController's had an Object ID that matched the error. It was presented as secondaryViewController from a SplitScreen. I removed that relationship segue, and did a manual Show segue instead, and it runs fine now.
tbrass84
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
Last seen
User for
Post
Replies
Boosts
Views
Activity
I have put tons of work into this with Obj-C, I refuse to rewrite everything to SwiftUI because Apple broke something.
https://www.youtube.com/watch?v=WWzh50TbW64
I get that, but 40GB seems off. Some of my other test devices only have 1-2GB
I keep having the same problem. Did you ever figure it out?
AND WHY IN THE WORLD are we not guaranteed an update when reload is called? This is not supposed to be a mini-app, and is supposed to be available at a glance, updated with dynamic content, so why create a system that cannot be guaranteed to refresh data as needed????
I created an incident.
Did you ever get this to work better? I'm having similar issues with the widget not updating at all.