ServoyCloudSupportSamplesOpen SourceCommunity

Mobile

Reference page for Mobile job configuration

Overview

Mobile jobs have properties split into four main categories:

Package

Name

The display name of the mobile application

Appstore ID

The ID as it will be known in the Appstore, i.e. "com.my-company.xyz"

Version

The version of the app, i.e. "1.4.2"

Description

A simple description of the application

Author

The name of the app Author

Author Email

The email address of the app Author

Icon

Optional. An icon that will represent your mobile app.

Environment

Application URL

The URL of the deployed NG Mobile application. Can be ServoyCloud environment URLs or self-hosted.

Mobile build/deploy type

The types of OS that will be supported.

Options

  • Android Debug - Selected by default when creating mobile job

  • Android for playstore

  • iOS

Plugins

Google Service-info.plist

File upload required when using FCM push notifications from the Used plugins list below. This file can be found in the Firebase console.

Google Service.json

File upload required when using FCM push notifications from the Used plugins list below. This file can be found in the Firebase console.

Lock Display Orientation

Locks the display to a portrait or landscape orientation. If your application is developed to be used in portrait orientation, lock display orientation to ensure a seamless experience.

Used Plugins

Available plugins, according to the operating system:

  • Bar Code Scanner

  • Camera

  • Camera Preview

  • Clear Text Traffic (Android Only)

  • FCM Push Notifications (Requires Google service files)

  • Fingerprint

  • Full screen

  • In-App Browser

  • Launch Navigator

  • Location

  • Network Information

  • Network Interface

  • Printer

  • Screen Orientation

  • QR Code Scanner

  • Vibration

Appstore

Android Keystore

File upload of Java .keystore file, required for signing of APK

Android Key Password

Java .keystore password, required for signing of APK

Android Keystore Alias

Java .keystore alias, required for signing of APK

Configure Android keystore

To create a Java keystore file and generate an Android keystore password and alias for signing an APK, you can follow these steps:

  1. Open a Command Prompt or Terminal: You can use your computer's command-line interface to generate the keystore file.

  2. Navigate to the Java JDK Bin Directory: You should have the Java Development Kit (JDK) installed on your computer. Open a command prompt or terminal and navigate to the bin directory of your JDK installation. This is usually located at C:\Program Files\Java\jdk1.x.x\bin on Windows or /usr/lib/jvm/java-x-openjdk-amd64/bin on Linux.

  3. Generate a Keystore File: Use the keytool command to generate a keystore file.

    • -alias: The alias for your key entry.

    • -validity: The validity period of the keystore in days.

    • -keysize: The key size (2048 bits is recommended).

    • -keyalg: This specifies the algorithm to generate the key pair (RSA in this case).

    • -keystore: This is the name of your keystore file.

Here's the basic command to create one:

// keytool -genkeypair -v -keystore my-release-key.keystore -keyalg RSA -keysize 2048 - validity 10000 -alias my-key-alias

  1. Store Your Keystore Securely: Once the keystore is generated, make sure to store it securely because losing it means you won't be able to update your app.

  2. Enter Information: You will be prompted to enter various information, including your name, organization, and a keystore password. Make sure to remember the keystore password; you'll need it later to sign your APK.

iOS Certificate

File upload of .p12 certificate file, required for signing of IPA.

iOS Certificate Password

.p12 certificate password, required for signing of IPA

iOS Provision file

File upload of .mobileprovision file, required for signing of IPA. This is your provisioning profile that specifies which devices can run your app during development. It also contains information about the App ID and certificate.

Configure iOS Certificate and Provision

  1. Apple Developer Account:

    Ensure that you have an Apple Developer account. You will need this to create and manage certificates and provisioning profiles.

  2. Create an App ID:

    1. Log in to your Apple Developer account.

    2. Go to the "Certificates, Identifiers & Profiles" section.

    3. Under "Identifiers," create an App ID for your app. Make sure it matches your app's Bundle Identifier.

  3. Create a Development Certificate:

    1. In the "Certificates" section, under "Development," click the "+" button to create a new certificate.

    2. Follow the on-screen instructions to create a Certificate Signing Request (CSR) using Keychain Access on your Mac.

    3. Upload the CSR to generate the development certificate.

  4. Create a Provisioning Profile:

    1. In the "Profiles" section, under "Development," click the "+" button to create a new provisioning profile.

    2. Select "iOS App Development" as the type.

    3. Choose the App ID you created earlier.

    4. Select the development certificate you just created.

    5. Choose the devices you want to use for testing (iOS devices must be registered in the Developer Portal).

    6. Give your provisioning profile a name and generate it.

  5. Download the Provisioning Profile:

    After generating the provisioning profile, download it to your Mac. This will generate your .mobileprovision file.

  6. Export the Development Certificate:

    1. Open Keychain Access on your Mac.

    2. Under "My Certificates," locate your iOS Development certificate.

    3. Right-click on it and choose "Export."

    4. Save it in .p12 format and set a password for it. This will generate your .p12 file

PreviousBuild and Deploy or BuildNextDesktop

Last updated