pis-effectus-app

Install dependencies: npm i.
Get the env files from an existing member of the project or the project's share knowledge. There should be 3 env files: .env, .env.staging and .env.prod. They should go in the root folder of the project and are gitignored already. You can check that you have the right set of keys by checking the .env.sample file.
Start on android or ios: android:{env} or ios:{env} (envs: dev, staging, and prod)
Get the firebase config files and follow the file placement inside the firebase zip file. This zip should be provided by the original development team.
In order to do this, make sure that you have the correct .keystore file mentioned in the configuration section.
go to android/app/build.gradle and search for versionCode and versionName, update them accordingly. The versionCode should always go up. TheversionName` should follow semver guidelines.
Run android:release:{env}
The generated APK can be found under android/app/build/outputs/apk/{env}/app-release.apk
Make sure to update the version number or build number if necessary. To do so search for CF_BUNDLE_VERSION_NUMBER and CF_BUNDLE_BUILD_NUMBER in the code. These are user defined variables that are used to set the version of all the build targets at the same time so they are always synced. You will need to change both instances where values are assigned to these variables. One is for debug and one is for release. As a precaution make sure that in the general tab of the build target you want to release, the fields were updated since they could have been changed directly there on a previous iteration and lost the syncing with the variables.
Select on Xcode the scheme of the build target you want to create the release for.
For the device select generic iOS device.
Then go to Product -> Archive.
After it is done processing and the archive succeeds the organizer will open. Here is where you can see all the previously generated archives.