How-to: Application identifier & application signature

The application identifier

The Application Identifier (or Application ID) refers to a string that uniquely identifies the application.

In case of iOS, it is the so called Bundle identifier, while on Android it is the application package name declared in AndroidManifest:

Application package name in Android

From the Android developer guide

A full Java-language-style package name for the application. The name should be unique. [...]

To avoid conflicts with other developers, you should use Internet domain ownership as the basis for your package names (in reverse). For example, applications published by Google start with com.google. You should also never use the com.example namespace when publishing your applications. [...]

Caution: Once you publish your application, you cannot change the package name. The package name defines your application's identity, so if you change it, then it is considered to be a different application and users of the previous version cannot update to the new version.

Where to place the application package name in the AndroidManifest .xml

Bundle identifier in iOS

From the iOS developer guidelines

A bundle identifier is a string you create for an application (such as com.myCompany.myCoolGame). The bundle identifier is used throughout the application development process to uniquely identify an application. For example, the bundle identifier is used to match the application you built in Xcode to the data you configured in iTunes Connect. [...]

For more information on setting the bundle identifier, see Information Property List Key Reference.

Where to place the Bundle identifier in iOS development

The application signature

The Application Signature refers to a string that correspondes to the Application Identifier. Any application that is using metaio Mobile SDK needs to provide an Application Signature string which has to match the Application Identifier.

Important: If the Application Identifier is changed, the corresponding Application Signature has to be changed as well.

Create an application signature

Creating an Application Signature is free of charge. The following steps are required:

1. Register at the Mobile SDK Developer Portal
2. Add the Application Identifier (i.e. Application ID / package name) of your application. This will instantly create an according signature that corresponds to the Application ID. You will receive it via email or you can use it directly from the developer portal.
3. Copy & paste the signature into your application for using it with the function CreateUnifeyeMobileIPhone() or CreateUnifeyeMobileAndroid() (depending on the according platform).

The steps in detail

Below we explain the steps to create an application signature in greater detail.

Register as a developer & login

Before using the developer portal, you have to register as a developer fore free. Please use a valid eMail address for registering, anonymous eMail accounts won't work. Before clicking on "Register", enter the captcha code (2) into the "Enter text" field. This is to make sure you are a human and no bot. Please note: You will not receive a confirmation eMail after registering.

After the registration, you can login:

Add your application identifier (ID) to your app pool

After logging in, you can add (1) & (2) a new application identifier to your pool of apps. Ater adding an Application ID, the signature is shown in your list of apps. Here marked in red and with point (3).

After adding an application ID, you'll receive an email with the Signature as well.

Optional: Add your "custom branding option" key to remove metaio branding from your apps

If you have purchased the custom branding option (CBO), you can enter it's key in "Licenses" in the developer portal to remove all mandatory metaio branding (watermark & splash screen) from your mobile apps.

Enter the Application signature

In general: Use search

Search for either CreateUnifeyeMobileAndroid or CreateUnifeyeMobileiPhone in your project, depending on the OS you are developing for. This variable takes one argument, which is your Application signature you created in the prior steps.

Other option for iOS

Look for UNIFEYE_LICENSE at the top of the UnifeyeMobileViewController.mm file, pass it your Application signature.

Other option for Android

Look for signature at the top of the Configuration.java file, pass it your Application signature.