Select the menu [Settings > Signing] item in the management console for the Signing setting to use for the app build. You can check the registered content after registering or creating (for Android) the Signing file.
Item | Description | |
|---|---|---|
1 | Name Search | Searches the Name information of the registered item. |
2 | Signing List | Displays the list of registered items. |
3 | Details | Enters the details of the item to be added or displays the details of the registered item. Name, Owner, and Access items are commonly applied, regardless of the deployment target. |
Item | Description | |
|---|---|---|
1 | Name | Enter the name of the item to register. |
2 | Owner | Enter the owner of Keystore (or Signing). (Automatically entered as the login account.) |
3 | Access | Set the access privileges for Keystore (or Signing). Depending on the access privileges, the Signing list that the user can use when creating the App is displayed differently. - share: Shared for the specified user - public: Shared for all users - private: Owner only |
If you select sharing for the specified user (share) when setting the Keystore access privileges, then you can select the person to whom you want to grant the privileges among the registered users.
You can check the users who have been granted keystroke access privileges. If you delete the user, then access privileges will be disabled.
If you select the public, private items, then the user selection function is not run.
Android
Item | Description | |
|---|---|---|
1 | Keystore Alias Name | Enter the Keystore Alias name. The Keystore Alias name must be at least 6 characters long. |
2 | Keystore Alias Password | Enter the Keystore Alias password. The Keystore Alias password must be at least 6 characters long. |
3 | Keystore File | Create the Keystore file or register the file you have. - Generate: Create the Keystore file in App Builder. - Upload: Register the Keystore file and display the registered file. The registered file is displayed in the form of a link and you can download the file by clicking the link. |
4 | Keystore Password | Enter the Keystore password. |
Please refer to the URL below for more information on Keystore.
iOS
Item | Description | |
|---|---|---|
1 | Certificate Name | Enter the iOS Certificate name. |
2 | Certificate Password | Enter the password for the registered iOS Certificate file. |
3 | Certificate File | Register the iOS Certificate file. |
4 | Provisioning Profile | Register the Provisioning Profile file. |
5 | Provisioning Type | Displays the Provisioning Profile file type. This is not an input item and one of the enterprise, app-store, ad-hoc, or development is displayed, depending on the Provisioning Profile file property. |
The app build can only be processed normally when the Package name registered when issuing the iOS Certificate file and the Package name entered when creating the app are identical.
Provisioning profile for in-house cannot be created with the wildcard app id (ex: com.nexacro.*).
Only the development certificate can create the wildcard app id Provisioning profile, and when creating Provisioning profile for deployment, you must make sure to select the Explicit app id (ex:com.nexacro.helloApp) to create it.
Please refer to the URL below for more information on the Certificate file and Provisioning Profile file.
macOS
Item | Description | |
|---|---|---|
1 | Certificate Name | Enter the macOS Certificate name. |
2 | Certificate Password | Enter the password for the registered iOS Certificate file. |
3 | Certificate File | Register the macOS Certificate file. |
The app build can only be processed normally when the Package name registered when issuing the macOS Certificate and the Package name entered when creating the app are identical.