Hey! Have you found anything on the topic? I would also like to adapt the "Ready to Scan" view but can't find any guidelines. (Would be fine to find at least an explicit prohibition.)

What else I've checked: Not using Touch ID on the physical device I removed all my fingers' scans on the physical device to confirm that sign in with Apple ID using code still works. (At first, I thought I would be asked for a password, to have the exact same scenario like on the simulator. However, without touch ID, sign in still worked.) 2. Sign up to the app for the first time In the https://appleid.apple.com/account/manage I removed my app from the list of authenticated apps and after that I tried to sign up with Apple ID in the simulator. Didn't work. 3. Hide email / share email I followed all possible routes there and neither worked. (I assume it has no impact, I just wanted to confirm). 4. Leaving the activity indicator in the password input overnight In that sense, it's not a matter of time... 5. Check in icloud.com (via browser) if there are no terms & conditions waiting for acceptance Nope. I've read somewhere that it was the case for some folks with test apple IDs accounts. However, I use my day-to-day Apple ID so all terms are already accepted.

Xcode Version 12.3 (12C33), Simulator Version 12.3 (940.20), tested in iPhone 12 Max simulator with iOS 14.2 and 14.3 and the bug still occurs. On the physical devices with iOS 14.2 and 14.3 works perfectly fine. I've experienced the bug with my own app and example Juice app. How to upload an app to the AppStore if sign in with Apple is the only authentication method? Does Apple really expect us to build alternative login path just for the review process to work around a bug in their own official authentication method? Please, provide any status. Do you know the cause? What is the plan? When can we expect this to be fixed? How should we proceed while waiting for the fix?