TMS Service

Introduction

In order to upload applications to server and deploy them successfully on devices, following conditions should be met:

  • Manifest files should be adjusted to have required metadata

  • apk files must be signed with appropriate keys

Adjusting the Manifest File

Fields below should be in AndroidManifest.xml, under manifest -> application -> meta-data tags, as name-value pairs.

Name
Type
Length
Description
Example
Required

app_name

String

At most 20

Application name with application type prefix

“LYL_COMPANYNAME”

or

"BNK_ID_COMPANYNAME"

Yes

app_model_type

String

At most 8

Model type name (should match with model type name in ATMS)

“400TR”

Yes

app_version

Integer

-

Version of the application

"1"

Yes

Separate apks should be created for 400TR, 1000TR, X30TR devices. The apk prepared for 400TR should have 400TR information in the XML file. The apk prepared for 1000TR should have 1000TR information. The apk prepared for X30TR should have X30TR information.

// for app_name
// if you are Retail developer then "LYL_COPMANYNAME" 
// if you are an Bank developer "BNK_ID_COMPANYNAME"

Example 400TR:

Retail:

<manifest ... >
    ...
    <application ... >
        ...
        <meta-data android:name="app_name" android:value="LYL_COMPANYNAME" /> 
        <meta-data android:name="app_model_type" android:value="400TR" /> // For 400TR devices
        <meta-data android:name="app_version" android:value="40000110" /> // Change Android  Version major/minor/build into integer. We kindly request this change. Version no must start with 400. Example: 40000110.
     </application>
...

Bank:

Example 1000TR:

Bank:

Bank:

Example X30TR:

Retail:

Bank:

To convert version name to manifest data, you can use following example in your build.gradle

Last updated