Isn't it ironic, to login to this forum on a new browser - guess what?! Apple requires 2FA. Yet they reject our apps for when we employ 2FA ourselves. As always, Apple is a hypocritical "Do as WE say....not as we do".
I have a primary app that has always used 2FA for four years now - Apple has always gone through the app register process using one of their own internal phone numbers and in four years have only rejected an app update once. We explained they have done it before (for years) - the reviewer somehow managed to find that registration (or phone number) and were able to get the app registered. App was always accepted without the need of a special account.
So...they CAN do it. But it always seems to come down to who is reviewing your app on what day. This week, we have submitted another app (on the same developer account as the primary app) and we are getting constant app rejection for the SAME 2FA authentication scheme as our primary app.
Its not about security for the reviewers, its about convenience. They CAN do it....some chose not to and reject your app as a result. Zero consistency...which is Apple's hallmark in the world of software development. Part of the app review process is validating the app is secure, doesn't contain malicious code, isn't fraudulent, etc....and the first thing Apple does is reject your app because you employ stringent 2FA security.
Again....the irony....or is it hypocrisy?
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags: