I have to say that this is yet another serious flaw in the Swift framework. You have to write your code on the assumption that the initializer for a view may be called multiple times, but this is highly inefficient and it causes a problem where you can easily have race conditions. I see no way to have nested models where an item can link to an array of items, for example, because that requires a query in an initializer that can create an infinite loop. Combined with Xcode's terrible debugging, this is infuriating.

I tried adding App_Uses_Non_Exempt_Encryption NO to Build Settings, but that did nothing.

I found this on Stack Overflow: *** SO *** Info.plist is not visible as a separate file until you add non-standard values to it Do you see the Info.plist in your project? Do you see the values of it reflected under [Blue Project Icon in Project Navigator] -> Targets -> [Your Target Name] -> Info? Did you try to add a custom value to it? (this will trigger it to become visible) See: https://stackoverflow.com/a/67896587/2804585 *** end SO *** Maybe you're thinking it's solved? Think again! Now it reports no errors or warnings on appstoreconnect, but it still won't let me add the build to my submission, so I can't add for review!

I got it to work by building from Xcode. Simply letting Apple build it when you push a commit wasn't good enough! Well, at least this time. We'll see on the next try... maybe we will need some other incantation.

For anyone still having this issue: Debug -> Debug Workflow Uncheck "Always Show Disassembly"

Another oddity: GeometryReader doesn't just read the geometry. It actually takes up space in the view! I suppose that's a feature, not a bug, right?

The error I'm getting: Thread 1: Fatal error: <UpdateCoalescingCollectionView 0x3037efc30> is stuck in a recursive layout loop. This can happen when self-sizing views do not return consistent sizes, or the collection view's frame/bounds/contentOffset is being constantly adjusted. To debug this issue, check the Console app for logs in the "UICollectionViewFeedbackLoopDebugger" category. Collection view: <SwiftUI.UpdateCoalescingCollectionView: 0x156f96a00; baseClass = UICollectionView; frame = (0 0; 852 149); clipsToBounds = YES; autoresiz

It turns out that the problem isn't with GeometryReader, it's with LazyVGrid. I'm not clear on why, but my grid with 5 columns doesn't always report the same size. I can make it work by adding a 6th column that doesn't get used in the view. Very odd.