DRIVER-Android | Android client for adding DRIVER records

To set up Android Studio to build and run this project, there are a few steps you need to perform first.
Generate a keystore
Generate and host a certificate file
Build models.jar file for the DRIVER environment's default Record Schema
(Optional) Set up Google Single-Sign-On (SSO)
Set up project configuration files
Build for release
DRIVER uses Gradle to dynamically generate a models.jar file that will contain the default Record Schema for the application for the initial model class definition, the backup model classes in case of update failure, and also for running tests. To trigger Gradle to build this file on a DRIVER environment, determine the UUID of the Record Schema you want the application to use and in a web browser load the URL https://{your-driver-domain}/api/jars/{schema-uuid}/. You should get back a 201 Created response while the Gradle process builds the models.jar file asynchronously. After a minute or so, refreshing the page should produce a 200 OK response. Once you get that response, if you append ?format=jar to the URL, it will then download the file. Note If you do not get a 200 OK response after several minutes, check: Is driver-gradle running on the celery server? Is there any output in /var/log/upstart/driver-gradle.log when you reload the /api/jars/ URL? If there is no output, restarting the service with sudo service driver-gradle restart often resolves communication issues. You may need to reload the /api/jars URL again after to trigger a new build. Once downloaded, copy the models.jar file to app/src/main/assets/models.jar.
Is driver-gradle running on the celery server?
Is there any output in /var/log/upstart/driver-gradle.log when you reload the /api/jars/ URL? If there is no output, restarting the service with sudo service driver-gradle restart often resolves communication issues. You may need to reload the /api/jars URL again after to trigger a new build.
This will enable users to sign in with their Google account using OpenID, instead of requiring them to have a username and password set up. Note The Android app requires users to have at least Analyst permissions within DRIVER to use, but users created by SSO default to Public permissions. Users created this way will need to have their account permissions upgraded by an Administrator user to be able to use the app.
Create Android OAuth credentials in the Google APIs Developer Console For OAuth to work your environment must already be configured with OAuth credentials for front-end use - it may be appropriate to configure these under the same account.
Download the credentials JSON file
Copy the credentials JSON file to the DRIVER-Android app/ directory.
If starting a new Android project, in the DRIVER-Android repository, create a configurables.xml file from the template:.
Set the URL for your DRIVER API server in configurables.xml under api_server_url.
Set the URL to the hosted certificate file in signing_cert_pem_url.
Set the label for the default Record Type (eg. "Incident") in record_type_label. Note: You can see all Record Types by going to https://{your-driver-domain}/api/recordtypes/.
Set the UUID for the Record Schema the models.jar file was made from in backup_jar_schema_version.
(For SSO) Set the Client ID for the target environment's Google APIs Developer Console "Web Application" credentials (These should be found in oauth_client_id of the appropriate group_vars file) in oauth_client_id.
Once the project configuration has been set up, you can use Android Studio to build and test the app. To build a APK for public release, go to Build -> Generate Signed APK... and follow the prompts. Assuming building is successful, you will have an app-release.apk file. This file can be placed at any secure web-accessible location and downloaded to users' Android phones.