search

ProgressNS / sidekick-feedback

This repository is for feedback regarding NativeScript Sidekick. Use the issues system here to submit feature requests or vote for existing ones.
45 stars 9 forks source link

Incorrect Certificates #241

Closed delanick closed 6 years ago

delanick commented 6 years ago

I move between projects a lot, and I see the reason I'm getting ARCHIVE FAILED errors is because Sidekick keeps using the incorrect certs and mobileprovisions for my apps. It doesn't keep track of which files each app uses, can you guys please correct this?

ggarabedian commented 6 years ago

Hello @delanick,

Actually, the behavior you describe is the intended one for the management of certificate and mobile provisions in Sidekick. The decision for this implementation was reached after a lot of internal discussions and user feedback. The conclusion was that most people use a single certificate for their applications and this implementation would benefits them the most.

Nevertheless, we continuously look for ways to improve the UI and overall experience with the certificate management and while we cannot make any promises, we will investigate if we have any options to extend this behavior to cover more scenarios.

delanick commented 6 years ago

Hi @ggarabedian I find that impossible to believe. I understand the use of one certificate, but each project requires its own mobile provision, and that's the part that needs to change each time...

ggarabedian commented 6 years ago

@delanick, we agree that the current behavior can be improved by adding an option to store the code signing assets per project and not globally, and let the user choose which approach he wants to use. To this end, we have logged this request in our backlog. While I cannot give you any specific time frame for when this will be available, we will try to find its place in our current roadmap and implement it as soon as possible.

delanick commented 6 years ago

@ggarabedian Amazing, thank you! :)