Same problem here. Any solution on this so far? I can hardly imagine Apple removed a disabled tab bar item property?

Same problem. App is approved within 24 hours. Subscriptions and App Store Localization show "Waiting for Review" ... since 5 days already. Could it be that I missed something on App Store Connect. A pain this procedure!

Done! https://feedbackassistant.apple.com/feedback/11839492 BTW ... can you confirm that the scope of a Sandbox Tester is the logged in Apple ID? Id est the entered Sandbox Testers can be used by all apps registered within the Apple ID? Is that correct?

App Store Connect (login) Users and Access Sandbox Testers Create a sandbox user. After that, try to toggle the INTERRUPTED PURCHASES switch. It has no effect. Once enabled, it remains enabled. Impossible to disable. APP STORE COUNTRY OR REGION changes reflect correctly after being changed. Before using FB, I'd like to have a confirmation that above behaviour can be reproduced by someone.

Thanks for your answer. I'm neither referring to consumable subscriptions, nor to Family sharing. I'd like to use a UID in my app, which persists across devices for the same Apple ID. This should serve as substitute for my missing app's User Account. It would allow in-app purchase restore in case the app was deleted from the device. iCloud/UserRecordID comes close to my requirements, but not everybody uses an iCloud account.

Is this not possible or doesn't anybody know? Shall I rephrase?

I don't see a yellow sign in front of the VC, but but a red arrow at the right side of the VC. When I select it, I see the list of all the errors. I take the first one in the list from the top, which belongs to cell 16 (numbered from top to bottom). It says "Missing constraints". So I select "Add missing constraints" and all of a sudden, 6 of 10 warnings are gone. Checking which contraints were added, I see that nothing (!) changed to my constraints. Hence Xcode didn't change anything, but decided to cancel 6 warnings. Besides this, please look at my example above (the Reset settings button). This one is pretty simple and there is virtually no room for mistakes (= wrong/bad constraints set by user). Ignoring warnings was what I did until now, but that's at the very best a workaround, no solution. I'd like to find the reason for these warnings.