* Add react-native-legal
* Update package-lock.json
* Update Podfile.lock
* Git ignore the results of the license gathering script
* Run "npx react-native legal-generate"
* Update .gitignore
* Type navigation in About
* Add link to About to show licenses
* Update strings.ftl
* Add step into build process
* Add jest mock
* Add npm script for legal-generate
* Update project.pbxproj
* update react-native from 82.1 to 83.4 (includes react@19.2)
* Update Podfile.lock
* Create react-native+0.83.4.patch
There seems to be a known issue in React 19.2 that makes us hit errors during development with this code in regards to using realm.
https://github.com/realm/realm-js/issues/7086https://github.com/facebook/react/issues/35126
* restore flow
* add two new RN file exceptions to flow
* pin react/types to ^19.2.0B
---------
Co-authored-by: Johannes Klein <johannes.t.klein@gmail.com>
* Update package.json
* Update AppDelegate.mm
* Update Podfile
* Update .gitignore
* Update link-inat-model-files.sh
* Add plist file to project
* Update project.pbxproj
* Add analytics package
* Update project.pbxproj
* Update PrivacyInfo.xcprivacy
* Basic screen tracking
* Basic button press logging to firebase
* Update package-lock.json
* Update Podfile.lock
* Add Android setup
* Update .gitignore
* Add analytics mock
* Ignore rubocop warning here
* Create GoogleService-Info.example.plist
* Create google-services.example.json
* Add instructions to set up Firebase configs
* Update e2e_ios.yml
* Update e2e_android.yml
* Better plural
* Use specific XCode version in e2e CI
* Update GoogleService-Info.example.plist
* Revert "Update GoogleService-Info.example.plist"
This reverts commit 0bc0ed4862.
* We need an actual real app id or we get a crash during app start
* My bad, we do need both files for building
* Also set API key
* Add comments
* Add comment
* Update Podfile.lock
* Revert "Use specific XCode version in e2e CI"
This reverts commit cbd63d1b5d.
