Posts

Post not yet marked as solved
3 Replies
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.
Post marked as solved
1 Replies
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.
Post marked as solved
22 Replies
Happening for my Series 4, as well. I really hope that Apple fixes this process — this is at least the third time this has happened in the past 6 months, and losing multiple days of being able to run and debug on-device is incredibly frustrating.
Post not yet marked as solved
2 Replies
I have been dealing with this same issue and pulling my hair out. Have you (or anyone else) made any progress on fixing this?