ProgressNS
two factor auth locks up Sidekick during publish step for iOS
If you have two-factor auth enabled on your Apple ID, Sidekick will get stuck during the publish step (after entering your Apple ID credentials).
Apple no longer allows you to turn off two-factor auth, so those of us using it are locked in and can't use Sidekick for iOS cloud builds.
Thanks for bringing this to our attention. We have internal task for enabling support for Apple account 2FA and will reprioritize it accordingly.
@geoker I found simple solution for this problem by sent invite (with role admin) to other apple id account isn't use two factor auth
Is there an update for this?
Apple requires 2 factor authentication for paid developer accounts--so I believe it requires 2 factor auth for anyone trying to publish to the app store.
My sidekick is getting caught on the "Publish to App Store" step. My guess is it is because of the 2 factor auth issue (Sidekick never asked for the 2 factor auth code, so I know it did not fully register my account). Does this mean that Sidekick is not currently useable to publish apps to the app store?
If so, that seems like a pretty big deal that should be stated clearly.
UPDATE: I'm not aware if sidekick has addressed this. But, since my post in January, I have been uploading directly to the app store using the cli. Specifically, I do the following:
-
$ tns build ios --provision "[specify provisioning profile you want to use]" --bundle --release --forDevice --env.uglify --env.aot [can also include any env.variables...] -
from that, it tells you where the updated ipa file is, like:
/Users/[username]/[app file]/platforms/ios/build/Release-iphoneos/[app name].ipa -
$ tns publish ios --ipa /Users/[username]/[app file]/platforms/ios/build/Release-iphoneos/[app name].ipa -
enter apple id, and password for the app, and good to go from there.
This is using NS 5.3+. I have heard that the $tns publish command does not work well with NS 5.4, and don't know about NS 6.0
