Open muuvmuuv opened 6 years ago
@muuvmuuv, the reported issue is identical to the one in #289.
At this moment, the Code Signing Assistance does not work with paid Apple IDs because they have two-step verification or two factor authentication enabled. We understand how restricting this limitation is and introducing support for paid Apple IDs for publishing and automatic generation of temporary iOS certificates and mobile provisions is on our road-map. Unfortunately, the implementation of this feature is complex and requires a lot of development effort, which is why we cannot give you a precise time frame for when it will be released.
As a workaround, you can test the Code Signing Assistance by creating a new Free Apple ID and use it to generate the temporary code signing assets.
I hope this is of any help.
@ggarabedian okay I understand, sorry for creating a duplicated issue (I thought I searched even closed issues for this). I'll try it with creating a new account, thanks for the hint!
@ggarabedian you also have the issue of not being able to publish to the app store because of 2FA. In that case we can't use your idea of a temporary free apple ID, we have to publish under the client's corporate name. This forces us to use a third party tool, appuploader. They figured out how to make it work.
@PacSD totally forgot about that! So the only way is to implement 2FA in Sidekick...
Please, provide the details below:
Did you verify whether this issue has already been reported here?
Yes
Tell us about the problem
If I'm trying to login with "iOS Auto Generate Provisioning Profile and Certificate" it fails after Apple is asking for 2FA
Which platform(s) does the issue occur on?
macOS
Provide the following version numbers that the issue occurs with:
Does this issue happen every time?
Yes
Send the client logs
https://we.tl/t-NhEjFDB8gV