I'm trying to test IAP in my Mac App Store app before submitting an update, but even after deleting every single trace of the installed app I can find, it shows the "sign in to use this application on this computer" prompt with the Apple ID filled and greyed out so I can't change the sandbox user account.I've searched high and low and can't find any comprehensive information about testing with sandbox accounts on macOS, much less anything about this specifically. What can I do?

Our app saves its data to iCloud by default. In most cases, this is working as intended & the data can be synced across devices with no problems. But recently, in testing, we discovered a situation where it's possible to save data before the NSMetadataQuery finishes & starts downloading the cloud files. When this happens, the query will then finish, and return the NEW file (with no other versions or conflicts). Is there a way to ensure that writing a file (version A) to ubiquitous storage when another version (version B) exists in the cloud is treated as a conflict, rather than just stomping all over the other version? I've tried querying the file metadata for the file URL (NSURLIsUbiquitousItemKey, NSMetadataUbiquitousItemDownloadingStatusKey, NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemHasUnresolvedConflictsKey) before saving, but it just returns nil.

The rejection states:The key LSMinimumSystemVersion in the Info.plist file has the value '$minimumSystemVersion', which is invalid. This string indicates the minimum version of macOS required for this application to run and must be of the form n.n.n where n is a number. For more information, see the Information Property List Key Reference.But the key's not even present in my Info.plist, nor is the string '$minimumSystemVersion'

When I try to run my iOS app through the Leaks instrument in the simulator, very shortly after launch, without fail, it will stop with the error "An error occurred trying to capture Leaks data"All the disclosure says is "Error retrieving leak information." I can't find any other information. Checking the console view, it just shows a normal run up until "<End of Run>"I've tried doing a clean build, deleting my derived data, uninstalling the app from the simulator, restarting Xcode, rebooting. I have no idea what to do.

I have an editor view that's broken up into several subviews. The model is a relatively small struct, but it does have a couple properties that can be variable-length arrays.The problem I'm having is after I add one entry to any one of these arrays, the view stops updating:struct ChecksView: View { @Binding var checks: [Check] var body: some View { HStack(alignment: .top, spacing: 0) { Button("add prereq", action: { self.checks.append(Check()) }) VStack { ForEach(self.checks.indices, id: \.self) { i in CheckView(check: self.$checks[i]) } } } } }In this subview, the first time you tap "add prereq", it will add to the array & update the UI. But every subsquent time, nothing updates until you navigate away & return. What am I doing wrong?

When we try to add localized info (what's new, description, etc.) we get a whole bunch of errors: Japanese The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Japanese Description couldn’t be saved because another field in this localization is invalid. Japanese Keywords couldn’t be saved because another field in this localization is invalid. Japanese Marketing URL couldn’t be saved because another field in this localization is invalid. Japanese Promotional Text couldn’t be saved because another field in this localization is invalid. Japanese Support URL couldn’t be saved because another field in this localization is invalid. Japanese What's New in This Version couldn’t be saved because another field in this localization is invalid. We have 2 versions of the app on the store, iOS & macOS. Both have the same name, because they're the same app. They predate the ability to add Universal versions of iOS/macOS apps. Could this be the cause of the error? We really don't want to have to change the name of either of them.