Warning

This repository hasb been archived. You can find the current cleema code on Open Code

Cleema Android

TOC

• Cleema Android
• TOC - Prerequisites - Setting things up - Starting the app locally - Debug deeplinks
  • Deployments
    • Deploy a new version to Testflight
    • Release version

Prerequisites

• Get Android Studio as we will be using it as an IDE

  • Enable "LiveEdit" hotload your code changes(up right of the "running Devices" tab)

• Get the correct Ruby version

  • With chruby
    • Depending on where you install your ruby version, you might need to add the location to your ~/.zshrc. Example: RUBIES+=( /opt/jruby-1.7.0 "$HOME/src/rubinius" ) -With rvm

Setting things up

Run the following commands in your Terminal before starting/developing. Requires the correct Ruby version from the step before (Doesnt work with the default mac ruby due to permissions, using sudo is bad practice)

bundle install
brew bundle

The project uses a secret.properties file (and a keystore.properties, not relevant for local development) for API tokens etc.

For a local development setup use the secret.local.properties and replace the baseToken with the IOS_LOCAL_ACCESS_TOKEN from your local backend:

cp secret.local.properties secret.properties

Alternatively you can set both your local backend and app to your own custom API token for development or use the .env for iOS & Android App from the Bitwarden

Starting the app locally

Make sure you have an Android SKD installed locally (check `File -> Settings -> Languages & Frameworks)

Started via android studio (top right). This will start a virtual android phone on which your app is run

Debug deeplinks

1. Reset all links on device / emulator via adb:

adb shell pm set-app-links --package de.cleema.android 0 all

2. Re-verify them:

adb shell pm verify-app-links --re-verify de.cleema.android

3. Check results:

adb shell pm get-app-links de.cleema.android

Output:

 de.cleema.android:
ID: 869a25b4-e918-4cbd-a3ca-16d3bfc9bf53
Signatures: [8B:79:8B:E2:22:3D:A8:D3:AD:5B:F8:F9:B5:28:FF:1D:CF:C9:A5:0F:FE:23:EC:10:B7:CB:97:B8:35:FB:1A:DB]
Domain verification state:
  cleema.app: verified

Output for the SHA256 for Signatures has to match $fingerprint in assetlinks.json. State 1024 (instead of verified) means a mis-match.