Hugo Gresse

I tried switching to this lib, in production the accuracy dropped a lot (around 300m). Removing ACCESS_COARSE_LOCATIN improved slightly but still ~120m. So I reverted back to https://github.com/react-native-community/react-native-geolocation version 2...

@react-native-community/geolocation has a new v3 version which also bring the Play geolocation API. I did not test the differences though, will do later this year, but I had no issue...

Our repo is over 8gb, this is preoccupying :/

it should redirect to the home page probably: https://openfeedback.io

Hey guys, just submit a PR ;)

Sure, fill free to give it a shot

This issue needs more attention. Potential solution: - the cocoapods version installed by the CocoaPodsPackageManager somewhere [here](https://github.com/expo/expo/blob/main/packages/%40expo/package-manager/src/ios/CocoaPodsPackageManager.ts#L54) should match the gemfile one - let the user have an option to...

I'm using pod-install without expo, so I had to use the trusty ``` - name: Change cocoapods version run: sudo gem install cocoapods -v 1.14.3 #https://github.com/facebook/react-native/issues/42698 ``` It could be...

I've spent to much time looking into why the timestamp was not adressing the timezone correctly. I've arranged @nthgol answer for Luxon as followed ```ts const getDateTimeFromComponent = ( jCal:...

I had the same issue, somewhere before I probably forgot to update the `AppDelegate.h` (header file) Linked to the update in version 0.68.4: Ref : https://github.com/react-native-community/rn-diff-purge/blob/release/0.68.4/RnDiffApp/ios/RnDiffApp/AppDelegate.h ``` #import #import @interface...