* Add Fastlate app store metadata files as Crowdin translation sources
* Update i18ncli.js to move and rename translations so Fastlane can use them
* Update `fastlane prod` so it prompts for public release notes and cues a new
release in the App Store that still requires the manual attachment of a
build
* Add `fastlane android upload_metadata` to upload metadata to Play Store
Closes#2248
---------
Co-authored-by: Ken-ichi <kenichi.ueda@gmail.com>
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
* Updated to Fastlane 2.222.0
* Set up basic fastlane task to make a version in the App Store
* Remove iPad, MacOS, and Vision targeting
* Added note about metadata sync not working
* Documented fastlane prod behavior in the README
* Add activity indicator to fetch location
* Add e2e location mock (#643)
Adds a mock for fetchUserLocation intended to be used with e2e tests. `MOCK_MODE=e2e` must be in the ENV for this to work.
---------
Co-authored-by: Ken-ichi Ueda <kenichi.ueda@gmail.com>
---------
Co-authored-by: Johannes Klein <johannes.t.klein@gmail.com>
Co-authored-by: Ken-ichi Ueda <kenichi.ueda@gmail.com>
I'd rather not do this but I wasn't able to figure out how get Fastlane to
automatically detect both of the provisioning profiles we need, because with
the multiple targets we need to support sharing we now need two provisioning
profiles.
* Add different env files to gitignore; update react-native-config
* Set different staging and production .env files in Android
* Add different envfiles to podfile
* Use podfile to check for .env.production and .env.staging files
* Update README
* Update fastfile to automate distribution/rollout for iOS and Android
* v0.1.1+34
* Tweaks to try to get Android to use production API via Fastlane
* v0.1.1+35
* Point production to .env instead of .env.production
* v0.1.1+36
Configures fastlane to automate our current release process of making a git tag, making a git release, building, and pushing to the Play Store internal track and Testflight. See README.md for details on setup and usage.
Co-authored-by: Amanda Bullington <albullington@gmail.com>
