I was still experiencing this in beta 2 and above, including the RC. It turned out that in the long-ago, I had actively disabled the "new" SPM PIF builder so I wasn't using the builder fixed by the above pull request. Changing that setting fixed it for me: defaults write com.apple.dt.Xcode IDEEnableNewPackagePIFBuilder -bool YES

You note that you have removed NSUserTrackingUserDescription from Info.plist, but your rejection from App Review explicitly states that the binary is what is referencing App Tracking. App Store Connect does decompilation of your binary and examines the libraries that are linked and used. I would triple-check that there is no reference ANYWHERE in your codebase to ATTrackingManager (including in third-party libraries). I would also double-check that if you have any additional targets, NSUserTrackingUserDescription has been removed from all of their Info.plist as well.

Happening to me as well.

The problem is almost certainly with this line: if ((authViewModel.currentUser?.id = collection.uid) != nil) { I'm not sure if it's intentional, but that line is setting the AuthViewModel.currentUser.id, rather than checking for equality. If you want to check for equality, you need to use == and remove the != nil portion. Since you are setting the value, that observed object publishes a change while SwiftUI is calculating its view updates. If you are actually intending to set the value, then you should do it some other way — perhaps before this view is created, or, less optimally, in .onAppear.