Android Touchscreen Deployment

Android Touchscreen Deployment

Objectives

Create the FullCount Touchscreen Android Application Bundle (.aab)

Deploy to the Google Playstore

Deploy to local device

Prerequisites

  • Android Studio 2.1.3 (min at the time of this writing)
  • JRE 1.6.0_45 (min)
  • Android Keepass access (Google Play developer Account and Android keys passwords)

Instructions

1. Open Android Studio

2. Make build changes

  • In File  [ FullCount_GeckoBrowser -> app -> build.gradle ]  find ‘defaultConfig’ block.
    1. Increment versionCode by 1
    2. Increment versionName to next determined version
    • versionCode must be greater than any previous versionCodes used, and less than MAX_INT

build-defaultConfig

  • Ensure Build Variant is set to ‘release'

Build Variants

 

3. Generate .apk

 

  • Toolbar -> Build -> Generate Signed Bundle / Apk…, Ensure 'Android App Bundle' is selected then click 'next'

 

  • Fill in All fields

Key store path:  path to [ android_fcpos_keystore.jks ]

Key store Password:  keepass ->android_fcpos_keystore

Key alias:  use existing (fc_pos_key)

Key password:  keepass ->FullCount_GeckoBrowser apk key

Select Next

Enter Master Password: keepass -> android apk master password

Enter destination folder. This is where the .apk will be placed.

Ensure Build Types to bundle are selected, generally any '...release'

Select Finish

 

4. Deploy to Playstore

 

a.  Navigate to Googles Developers Console at [ https://developer.android.com/index.html ]

  • Log in using keepass -> GooglePlay Developer Account username and password

b.  Select FullCount POS – Senior Living [x.x.x]

c.  In the left sidebar select ‘Closed Testing’ under 'Testing' and then 'manage track' for beta

 

d. At the top you will see 'Edit Release' or 'Create new release' button. Select it. see (1) below

  • Navigate to where the newly generated aab is and select
  • Once uploaded ensure all information is accurate
    1. versionName / versionCode
    2. Any manifest changes that were made for this release
    3. Add any relevant version information

Note: This will be viewable in playstore.

  • Publish to the beta channel

e.  Test app store release on FullCount Lab tablets  (Boot test, user functions test.)

  • Test users can be configured through (2) above.

f.   Once finished with testing, select ‘Promote release’ see (3) above

  • Timed release is configured for Production.

g.   Once the Promotion is complete you will need to go to 'Releases overview' from the left navigation and make it available via the playstore.

 

 

Debug Deployment

  1. Open Andoid Studio
  2. Import the android app, File -> New -> Import Project, the directory will be: \mobile\android\trunk\FullCount_GeckoBrowser\app
  3. Open Build Variant: Build -> Select build variant
  4. In the Build Variants window, select armDebug or aarch64
  • this will depend on the OS of the device you're deploying to.  32-bit devices will use arm, where 64-bit devices will use aarch.
  2. Make sure the Android device you want to use has USB Debugging turned on. This can be different per device / OS version so you may need to look up how to Enable/Navigate to Developer Options.
  3. When USB Debugging is turned on, connect your android device to your machine, if everything is working you will see your device as the target device:

  1. Finally hit the run button and the App should deploy to the Device

 


    • Related Articles

    • Post Central Deployment Tasks

      Post Central Deployment Tasks Objectives Complete necessary post-deployment tasks Prerequisites Access to Redmine Access to production database Access to fcadmin Access to deployment test server Instructions Send release docs Release docs are located ...

    • Remote Deployment Process - Java

      Deployment Process Determine if a valid argument has been passed in Only continue if downloadOnly, postDownload, fullDeployment, handleSuccess, checkHash, verifyApplications passed through. Lock file to stop deployment from running more than once ...

    • Central Deployment Process

      Run SQL scripts in http://sourcecontrol.fullcount.net/repos/internal/trunk/at-fullcount-model/src/main/resources/sql/nextDeploy Pause TeamCity test for fullcount-uptime-production-overnight. Download release war file from archiva for all ...

    • Pre Central Deployment Tasks

      Pre Central Deployment Tasks Objectives Complete necessary pre-deployment tasks Prerequisites Access to Redmine Access to production application server Access to Subversion Access to TeamCity Instructions Update Semantic Version Information See ...

    • Run Remote Deployment Process - Java

      Remote Server Configuration This has already been completed for all existing remote servers. Java 1.8 installed Tomcat located at /srv/tomcat XE database installed and running with fc_obj_owner user Directory /home/deployment exists Database backup ...