The open source codesigndoc tool runs a clean Xcode/Xamarin Studio Archive on your Mac, and analyzes the generated archive file. It collects the code signing settings that Xcode or Xamarin Studio used during the archive process, and prints the list of the required code signing files. You can also search for, export and upload these files using
If your project contains UITest targets, codesigndoc can scan for that, too. It runs the
xcodebuild build-for-testing action to create a test-Runner.app, and exports the necessary code signing files.
Collecting the files with codesigndoc ⚓
You can use
- Xamarin projects.
- Xcode projects.
The app does not have to be a native iOS app: you can use the tool with an app built with a third-party framework, such as Flutter, if you have an
You can install the latest version of codesigndoc with a simple one-liner or you can manually download and install the specific version you want to use:
In the below example, we’ll use the one-liners.
- Open the
- Go to your project’s folder.
- Enter the appropriate one-liner command, depending on your project type.
For an Xcode project:
bash -l -c "$(curl -sfL https://raw.githubusercontent.com/bitrise-io/codesigndoc/master/_scripts/install_wrap-xcode.sh)"
For a Xamarin project:
bash -l -c "$(curl -sfL https://raw.githubusercontent.com/bitrise-io/codesigndoc/master/_scripts/install_wrap-xamarin.sh)"
The tool will automatically scan your project and look for a
.xcworkspacefile and do the rest.
If the scanner does not find the files, open your
Finder.appand drag-and-drop your project’s
.xcworkspacefile into the command line in your Terminal.
Uploading the files to Bitrise with codesigndoc ⚓
Once the code signing files are collected,
codesigndocwill ask if you wish to upload the files to Bitrise:
Do you want to upload the provisioning profiles and certificates to Bitrise? [yes/no] :
If you wish to upload the files with
yesand press Enter.
Provide your Bitrise access token.
Please copy your personal access token to Bitrise. (To acquire a Personal Access Token for your user, sign in with that user on bitrise.io, go to your Account Settings page, and select the Security tab on the left side.) :
Select the Bitrise project as a target for the collected files:
Fetching your application list from Bitrise... Select the app which you want to upload the provisioning profiles Please select from the list:
That’s all, you are done!
If you wish to use automatic provisioning with our iOS Auto Provisioning Step, you only need to collect the certificate file(s). You can run
codesigndoc scan with the
--certs-only flag to do that.
You can also install and run
codesigndoc manually. For more information, check out the tool’s Readme!
Scanning for UITest targets ⚓
If your Xcode project has UITest targets, you can use codesigndoc to export the necessary code signing files and generate an
.xctestrun file. You need to do this if you want to run UI tests on real devices with the help of Bitrise - for example, with the `iOS Device Testing` Step.
To take advantage of codesigndoc’s UI test scanner, you need a scheme that has a valid UITest target that is enabled.
If your project is set up correctly on your machine, you can start scanning!
- Open the
Use our one-liner to launch the scanner and export the required code signing files:
bash -l -c "$(curl -sfL https://raw.githubusercontent.com/bitrise-tools/codesigndoc/master/_scripts/install_wrap-xcode-uitests.sh)"
This command runs the
xcodebuild build-for-testingaction to create a UITest runner .app file, and exports the necessary code signing files.
- Upload your files to Bitrise with codesigndoc.
Troubleshooting the UITest scanner ⚓
If the UITest scanner cannot find the desired scheme, follow these steps:
Make sure your scheme is valid for running a UITest.
It has to contain a UITest target that is enabled to run.
- Refresh your project settings:
- Select the Generic iOS Device target for your scheme in Xcode.
- Clean your project:
⌘ Cmd + ↑ Shift + K.
- Run a build for testing:
⌘ Cmd + ↑ Shift + U.
Manually installing and using codesigndoc ⚓
With manual install, you can specify which version of codesigndoc you want to use. Unlike with the one-liners used above, the manual install does not automatically run the
scan command in the folder you use it in: it merely installs the tool.
Check out the available versions on the releases page of the codesigndoc tool.
Download the release you want by running a
Note: replace the VERSIONNUMBER with the actual number of the codesigndoc version you want.
curl -sfL https://github.com/bitrise-io/codesigndoc/releases/download/VERSIONNUMBER/codesigndoc-Darwin-x86_64 > ./codesigndoc
Make the downloaded binary executable:
chmod +x ./codesigndoc
Done! You can now run the
scan command of the tool at any time:
## Xcode scanner ./codesigndoc scan xcode ## Xcode project scanner for UI test targets ./codesigndoc scan xcodeuitests ## Xamarin project scanner ./codesigndoc scan xamarin
Best practices ⚓
You get the most accurate result if you run
codesigndoc on the same state of your repository/code which is available after a clean
git clone, as that will be the state of the code after the build server checks it out (for example, you might have files on your Mac which are in
.gitignore, so it exists on your Mac but not in the repository or after a
git clone on a new Mac).
So, for the best results, we recommend you to:
- Do a clean
git cloneof the repository (into a new directory) on your Mac.
codesigndocin this directory (not in the directory where you usually work on the project).
It’s also advised to do a full Archive + Export (until you get a signed
.ipa) of your project from
Xcode.app first, and run
codesigndoc after that. The reason is that
Xcode.app might download or update profiles in the background during the IPA export. If you run
codesigndoc after you exported an
.ipa from Xcode,
codesigndoc will able to collect all the files.
You can upload, update, list, and delete iOS code signing files with the relevant Bitrise API. In this guide we show you how and in what order to use those...
You can manually specify the code signing configuration in your Gradle configuration so that your app gets signed during the build process.
You can create a signed APK using the Android Sign Step in your Bitrise workflow. This Step is configured to run if you have already uploaded your keystore file to...