Hi @dev-mgr-uk,
Definitely see your point and we’re working on making it easier! In the meantime (copy pasting from our other chat) I’d suggest you to follow this guide:
- To generate a Certificate: https://ioscodesigning.com/generating-code-signing-files/ - probably easiest to do it from Xcode
- To generate a Provisioning Profile: https://ioscodesigning.com/generating-code-signing-files/#generate-a-provisioning-profile - probably easiest to do it from Xcode
- Then Export the Certificate with the related private key (.p12 file): https://ioscodesigning.com/exporting-code-signing-files/
- Export the Provisioning Profile: https://ioscodesigning.com/exporting-code-signing-files/#exporting-provisioning-profiles
- Once you have these files (a Certificate with private key in
.p12
format, and a Provisioning Profile) you can upload them to Bitrise.io in the Workflow editor, under Code Signing, and just follow the rest of the guide here (Generating release outputs for Ionic -> “Build for device” section).
Once you get to this configuration phase it might also help to run the Bitrise runner / CLI on your own Mac, so that you can iterate on the actual config faster using the same tools (including the editor GUI) right on your Mac! Related guide: How to experiment with Bitrise configs locally, on your Mac/Linux
If you’d have any questions just let me know!
P.S.: for reference this is the official Cordova Code Signing documentation, applies for both Cordova and Ionic projects: https://cordova.apache.org/docs/en/latest/guide/platforms/ios/#signing-an-app