Skip to content

Security and Configuration

Jump to bottom
Andrew Limond edited this page Apr 16, 2024 · 1 revision

Lasta App Security and Configuration

Table of Contents

  1. API Keys Management
  2. Signing Configurations
  3. Additional Resources

API Keys Management

Google Maps API Key

The Google Maps API key is stored in the local.properties file, which is excluded from version control to keep it confidential. Follow these steps to manage the API key:

  1. Locate the local.properties file in your project directory.
  2. Navigate to the Google cloud dashboard for this project and find the api key there.
  3. Add the following line to specify your Google Maps API key: 
    MAPS_API_KEY=YOUR_GOOGLE_MAPS_API_KEY

Firebase Web Client API Key

The Firebase Configuration informaiton is stored in the google-services.json file. This file is also excluded from version control for security reasons. Here's how to manage it:

  1. Obtain the google-services.json file from the Firebase Console.
  2. Place the google-services.json file in the app directory of your Android project.

Signing Configurations

Keystore Configuration

The app's release version is signed using a keystore file (keystore.jks) and its corresponding properties file (keystore.properties). These files are crucial for securing the app's integrity and authenticity.

Keystore File (keystore.jks)

The keystore file contains the private keys required to sign the app. Keep this file confidential and secure.

Keystore Properties File (keystore.properties)

The keystore.properties file typically contains the following information:

storePassword=YOUR_STORE_PASSWORD
keyAlias=YOUR_KEY_ALIAS
keyPassword=YOUR_KEY_PASSWORD

Make sure to keep these properties file secure and exclude it from version control.

Additional Resources

This wiki page provides an overview of the security measures, API keys management, and signing configurations implemented in the Lasta Android app. Following these best practices ensures the app's security and integrity are maintained throughout its development and deployment lifecycle.

Clone this wiki locally