* 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 package.json
Without the babel plugin the app does not start because of an error with the new package.
* Update babel.config.js
* Update package-lock.json
* Switch to new package for Wikipedia text
* Update Podfile.lock
* Use new package in UserText
* Link underline was blue, now green again
* Make headings in user text the same as in the app
* Fix typo?
Not hundred percent sure about this, but MDN docs show no t tag and the original list in inaturalist has tfoot in this place here.
* Remove tag that is not supported on web
* Refactor making of html into helper function
* Update index.ts
* Create a snapshot test for build html function
* 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>
* Reapply "Update react-native-sensitive-info to 5.6.2 (#3346)"
This reverts commit 4bd596074c.
* Explicitly set keychainService to "app" for all calls to RNSInfo
So, apparently the default string used to save sensitive items changed from "app" to "default" between versions 6.0.0-alpha.9 and 5.6.2.
So if we install an app update built with 5.6.2 on top of our previous version (using 6.0.0-alpha.9) we can no longer find our previously stored secrets.
I am leaving the key as overridable by actual options propped in, in case someone wants to build a separate slice at one point. In contrast to accessControl which probably should not be a decision in engineerings court.
* Add comment
* Update test helpers
* Update react-native-sensitive-info
* Delete react-native-sensitive-info+6.0.0-alpha.9.patch
* Migrate sensitive info error handling
* Lint rules changes
* Add comment
* Remove incomplete type
* Add hasItem mock
* Update type
* Remove exported function getUsername
This is nowhere imported, used only in AuthenticationService. Have added the only function that makes use of getSensitiveItem( "username" ) = isCurrentUser to the Auth integration test instead.
* Update package-lock.json
* Update Podfile.lock
* Replace string with exported error code
* Add try catch to hasItem call
* Replace our fork of react-native-camera-roll with latest
published npm version
* Update package-lock.json
* Update Podfile.lock
* Create @react-native-camera-roll+camera-roll+7.10.2.patch
Copying over commits from our fork of camera-roll into a patch-package patch file. This corresponds to these two commits:
1.) "fix: add a stub URI after save w/ add-only permission (#1)
Attempting the fetch the URI of the newly-created photo requires PHOTO LIBRARY
permission, which results in an unexpected permission prompt. This prevents
that from happening by returning a stub URI which hopefully makes it clear
why it's not a real URI."
47b39c3d9d
2.) "feat: optionally save location when saving photo in iOS"
c49afe441e
