Background
To publish your app to the App Store on Thunkable Cross Platform ✕, we currently require users to turn off two-factor authentication. Apple recently made a change requiring new users and those that have upgraded to the latest iOS or MacOS to turn on two-factor authentication.
If you have two-factor authentication turned on, you will currently* not be able to publish to the iOS App Store.
Recommendation
(1) If you have not turned on two-factor authentication and would like to publish your Thunkable app to the iOS app store, we recommend that you do NOT turn it on.
(2) If you have recently turned on two-factor authentication, you have 2 weeks to turn it off. To do so, you will need to check your account for an email like the one below and follow the link inside to turn it off.
(3) If you have turned on two-factor authentication and it’s been longer than 2 weeks, you have two options. If you need to publish your app ASAP, you can create a new Apple ID and follow the instructions in (2) to turn off two-factor authentication. You will however have to pay for a new Apple Developer program membership ($100 /year). If you can wait to publish your app, we are working on a fix to enable publishing to iOS with two-factor authentication turned on.
*We anticipate a fix to take up to several weeks until it is available
Apologies for the inconvenience,
The Thunkable team
Apologies for the delay. We are almost in testing stage for allowing you to Publish to iOS with 2-factor turned on.
To set expectations, the new process will require a few additional steps that are required by Apple to verify your identity including generating an Account Certificate, and App Provisioning Profile and an App-Specific Password.
If all goes as planned, this should be ready for you to use soon.
The new 2fa workflow is out and here is what you need to know -
(1) If you have an account without 2fa, the way you publish will not change.
(2) If you have an account with 2fa, you need to following the instruction here.
Thanks to Jeremy and Donovan’s help, we were able to find the root cause of this issue, and are now working on a fix. We’ll let you know once it’s done.
Thanks, everyone, for building your apps with Thunkable!