Skip to content

Supported Client Types, Packaging Details, and Build Options

The cloud build service supports different build types, client types, and build options.

Supported Build Types

Build Type SDK Version UI5 Versions Supported Android Versions Supported iOS Versions Notes
Mobile Development Kit (MDK) and Customized Mobile Development Kit 6.3.0 (default version), 6.2.7, 6.1.3, 6.0.9 and 5.2.7 N/A MDK 6.3.0: 12.0, 11.0, 10.0, 9.0, 8.1, 8.0. MDK 6.2.7 and lower: 12.0, 11.0, 10.0, 9.0, 8.1, 8.0, 7.1, 7.0, 6.0. MDK 6.3.0 and 6.2.7: 15.7, 15.0, 14.8, 14.0. MDK 6.1.3, 6.0.9 and 5.2.7: 15.7, 15.0, 14.8, 14.0, 13.7, 13.0. MDK version 6.3.0 and 6.2.7 use: NativeScript 8.3.2 and Node 16.14.2. MDK versions 6.1.3 and 6.0.9 use: NativeScript 8.2.2 and Node 12.21.0. MDK version 5.2.7 uses: NativeScript 6.8.0 and Node 12.21.0.
SAP Mobile Cards (MCK) 21.1.8 N/A 11.0, 10.0, 9.0, 8.1, 8.0, 7.1 15.4, 15.0, 14.8, 14.0
SAP Asset Manager (SAM) 2205.0.3 (default version), 2110.0.3 and 2105.0.0 N/A SAM 2205.0.3: 12.0, 11.0, 10.0, 9.0. SAM 2110.0.3 and 2105.0.0: 11.0, 10.0, 9.0. SAM 2205.0.3: 15.7, 15.0, 14.8, 14.0. SAM 2110.0.3 and 2105.0.0: 15.3, 15.0, 14.8, 14.0, 13.7. 13.0. SAM 2205.0.3 uses: Mobile Development Kit 6.2.7, SAM Plugin 2205.0.300, NativeScript 8.3.2, and Node 16.14.2. SAM 2110.0.3 uses: Mobile Development Kit 6.0.9, SAM Plugin 2110.0.400, NativeScript 8.2.2, and Node 12.21.0. SAM 2105.0.0 uses: Mobile Development Kit 5.2.7, SAM Plugin 2105.0.004, NativeScript 6.8, and Node 12.21.0.

Note

For application error due to Could not find module 'tns-core-modules/file-system' or similar messages, refer to Metadata / Client Project Migration for application metadata migration.

Supported Client Types

Client Type Required Packaging Details Supported Build Options
Mobile Development Kit client See SAP Mobile Services, Mobile Development Kit
  • Build Version
  • Device App Name
  • Device App Display Name
  • Device App Version
  • Device App Details
  • Bundle ID (iOS)
  • Package Name (Android)
  • Secure Database Encryption
  • Android & iOS Builds: URL Scheme
  • Android Builds: Google Services JSON File, Binary Format
  • Multimedia: Application Launch icon
  • Create Debug-enabled Binaries
  • Signing Profile
  • SDK Version
  • Minimum Platform Version
Customized Mobile Development Kit clients
  • Build Job Name
  • Secure Database Encryption
  • MDK Project ZIP File
  • Android Builds: Google Services JSON File, Binary Format
  • Multimedia: Application Launch icon
  • Create Debug-enabled Binaries
  • Signing Profile
  • SDK Version
  • Minimum Platform Version
SAP Asset Manager See SAP Asset Manager
  • Build Version
  • Device App Name
  • Device App Display Name
  • Device App Version
  • Device App Details
  • Bundle ID (iOS)
  • Package Name (Android)
  • Secure Database Encryption
  • Android & iOS Builds: URL Scheme
  • Android Builds: Google Services JSON File, Binary Format
  • Multimedia: Application Launch icon
  • Create Debug-enabled Binaries
  • Signing Profile
  • SDK Version
  • Minimum Platform Version
Mobile Card Kit Client See SAP Mobile Cards.
  • Device App Name
  • Device App Version
  • Bundle ID (iOS)
  • Package Name (Android)
  • iOS Builds: URL Scheme
  • Android Builds: Deep Link URL (Android), Google Services JSON File, Certificate Authentication for OAuth (Android)
  • Multimedia: Application Launch icon
  • Certificate Authentication for OAuth
  • Create Debug-enabled Binaries
  • Signing Profile
  • Minimum Platform Version

Packaging Details Overview

Field Description
Build Job Name (Customized Mobile Development Kit client only) A unique build job name to replace the default name.
Mobile Development Kit Project ZIP File (Customized Mobile Development Kit client only) The customized Mobile Development Kit project file to upload. The file must be in ZIP format, and meet validation rules.
Device App Name A user-friendly name for the device application that appears as label on the device, such as My Weather App. The Device App Name is not the same as the App Name or the application ID property you configured when you defined the app, and becomes the default for this field.

Note: "Cordova" is a reserved word, so you cannot use it in the Device App Name.
Device App Version The application version.
Device App Display Name The label that appears on the welcome screen after you launch the app. This must be a String value with a maximum length of 128 characters. See the note below when building client type Mobile Development Kit Client with MDK 6.2 and later.
Device App Details The subtitle for the application, which appears on the app's welcome page. This must be a String value with a maximum length of 128 characters.
Bundle ID (iOS) The unique app identifier provided by the App Store. You can change the bundle ID to match the bundle ID of the provisioning profile that you uploaded while creating the signing profile used to sign the iOS Mobile Development Kit and SAP Asset Manager clients.
Package Name (Android) The unique app identifier. For Android apps, the package name used to sign Android Mobile Development Kit clients.
URL Scheme For iOS builds: The custom URL scheme that enables other apps to communicate with your app. For Mobile Development Kit, use the URL Scheme entry for both iOS and Android builds.
Deep Link URL (Android) For Android builds: A related web page URL for any card template, that enables the user to open the relevant web page for each card instance. For Mobile Development Kit, use the URL Scheme entry for Android builds, not Deep Link URL.
Google Services JSON File For Android builds: The Firebase Android configuration file associated with your app in your Firebase project. Use Browse to navigate to and select this file. The file is uploaded to the service when you save the Cloud Build configuration. To display the contents of the JSON file after upload, select Show Contents. To remove the uploaded Google Services JSON File, select Remove File.
Binary Format For Android builds: The packaging format to use for the build, including APK (Android Package Kit, the default) or AAB (Android App Bundle). Since Google requires that applications uploaded to the Google Play Store be built in the AAB format, select this option if that is your plan. To install an AAB binary without using the Google Play Store, you must download the AAB and use Google's bundletool to extract an install-ready binary from the AAB and install that binary. Refer to their respective documentation on bundletool for more details. For iOS builds, the packaging format is IPA (iOS App Store Package).
Secure Database Encryption Whether the database must be encrypted. True indicates the database should be encrypted. False indicates the database should be encrypted with a known key MDK (MDK >=6.2) or unencrypted (MDK < 6.2). Use the False option to debug the database content (this is meant to be used for development, debugging or demonstration purposes only).
Certificate Authentication for OAuth Set OAuth to use certificate-based authentication.

Note

When building client type Mobile Development Kit Client with MDK 6.2 and later: * If a value is provided in the Device App Display Name field, the same value is also used as the launcher name, which is the text under the application icon on the device screen. When specifying this value, please consider the launcher naming recommendations made by various app stores, and possible consequences if they are not followed. * Otherwise, the launcher name uses the value of the Device App Name field.

Supported Build Options

Build Option Description
Create Debug-enabled Binaries Whether to build the binary with debug enabled.
Signing Profile The signing profile with which to sign the binary.
SDK Version Select the SDK version to use for the build, or use the SAP recommended version.
Minimum Platform Version The minimum device operating system version required to install the binary.

Last update: October 19, 2022