You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you are done developing you app, the CLI should allow you to easily pack apk/ipa ready for submission to the store.
For iOS this involves at least two things to be automated:
Exporting an archive, that later can be signed with distribution certificates and submitted to the store.
Sign and submit to the store directly from the command-line.
The first will be more useful for larger organizations whit more strict security policies. It should create an Xcode archive that later can be opened in the Xcode organizer and submitted manually through the Xcode UI. The archive also contains app that can be signed and submitted to the AppStore from the command-line by more advanced users.
The second will be more useful for indie developers and small companies with less Bureaucracy that are ok to keep the distribution certificates in their keychain. It will also be useful for automated builds to submit automatically (similar to Telerik's companion app build). It would be extremely useful if this logs detailed distribution certificate and provisioning profile problems.
Having #558 in place will allow developers to sign the app with a given certificate. Ability to publish from the Command-Line is doable by directly invoking the iTMSTransporter command line executable.
Once you are done developing you app, the CLI should allow you to easily pack apk/ipa ready for submission to the store.
For iOS this involves at least two things to be automated:
The first will be more useful for larger organizations whit more strict security policies. It should create an Xcode archive that later can be opened in the Xcode organizer and submitted manually through the Xcode UI. The archive also contains app that can be signed and submitted to the AppStore from the command-line by more advanced users.
The second will be more useful for indie developers and small companies with less Bureaucracy that are ok to keep the distribution certificates in their keychain. It will also be useful for automated builds to submit automatically (similar to Telerik's companion app build). It would be extremely useful if this logs detailed distribution certificate and provisioning profile problems.
We need this elaborated for android.
Related iOS issues
Android
--key-store
options which is enough to produce APK ready for submissionThe text was updated successfully, but these errors were encountered: