When publishing your app to Google Play or the iOS App Store, it needs to be signed before it's sent off.


A Uno Project set up for signing can look like this:

	"Android": {
		"Key": {
			"Alias": "application",
			"AliasPassword": "<alias password>",
			"Store": "release.keystore",
			"StorePassword": "<store password>"

A file named release.keystore is expected to be found in the same folder as the project.

This file can be created by running the following command in your shell (keytool is part of the JDK):

keytool -genkey -v -keystore release.keystore \
    -alias application -keyalg RSA -keysize 2048 -validity 10000

The program will prompt you for an alias password and a store password, which should be the same as the respective values in the project file.

Note that only release builds are signed using the specified key. Debug builds are automatically signed using a debug key. To do a release build, use uno build --target=Android --configuration=Release.


Run the following command in your shell:

uno build --target=iOS --configuration=Release -adebug

Then follow the regular procedure for adding your signing certificate and submitting your app to the App Store.

Xcode Development Team IDs

Since Xcode version 8, Apple mandates code-signing even for debug builds.

For this to work you need to set a Development Team ID, and then Xcode will usually handle the rest automatically.

Your Team ID can be found here.

Uno attempts to automatically find an Xcode Development Team ID by querying the machine's code-signing identities and selecting the first valid one it finds. If this is not the correct one it can be set manually in an unoprojs as follows:

  "iOS": {
    "DevelopmentTeam": "YOURTEAMID"

It can also be set by passing the --set:Project.iOS.DevelopmentTeam="YOURTEAMID" flag to uno build, e.g.

uno build iOS --set:Project.iOS.DevelopmentTeam="YOURTEAMID"

The Development Team ID can also be set user-wide by adding the following to ~/.unoconfig:

iOS.DevelopmentTeam: "YOURTEAMID"

The file can be created if it doesn't already exist.


Error messages such as No matching provisioning profiles found are usually resolved automatically just by opening the generated Uno project in Xcode once by building with -adebug. Also make sure that the Development Team ID has been correctly set.

This page contains more information about troubleshooting certificate issues.