Publish Android APKs as Github releases as a part of Fastlane deployment

[DiagonalArg]

Like @kasbah , who was asking about a non-google fallback for location services, I am running a non-google phone (GrapheneOS). I see that iNaturalist itself makes .apk's available. Would Seek consider the same?

[kasbah]

Adding to F-Droid would also be nice.

[DiagonalArg]

Adding to F-Droid would also be nice.

O/T, but f-droid signs the packages themselves. I think better to use obtainium with the developer signed packages from github.

[kueda]

Hey folks. In general, if you have questions, feature requests (like this), or bug reports, please post them to the iNat Forum instead of here on Github. We use Github for organizing work that we've decided to do, not for discussing work that we might or might not do.

That said, we talked this over and agree it would be a good thing to publish these APKs on Github, albeit not a very high priority, so I'm just going to respecify this a bit:

• [ ] Add a step to our Fastlane build process to make a Github release and push the APK there like we do in iNaturalistReactNative
• [ ] Add an e2e test that ensures location does get fetched on an AOSP emulator (we already use an AOSP emulator so this is mostly just writing the test)

Also FWIW, this app uses react-native-maps, which will include the Google Maps SDK on Android and make it ineligible for inclusion in F-Droid. I'm not sure if it will run on GrapheneOS

[DiagonalArg]

@kueda / Point taken regarding the iNat Forum, though since it fits firmly within this present discussion, perhaps as a longer range plan, you might consider using, or making as an option, OpenStreetMaps, rather than GoogleMaps.

Thank you and your colleagues for all your work!