Verena Brodbeck

Yes we did, but only with the very basic tile set until now (nothing customized) and that worked. ```

UPDATE I edited [this statement ](https://github.com/rnmapbox/maps/issues/2163#issuecomment-1232988462): >~Seems that from v10 on, Mapbox enforces you to use their services.~ from my previous comment, because it can't be true. We now saw...

We see the same with `@react-navigation/native` version 6.0.13 ```JS const navigationRef = createNavigationContainerRef(); const navigate = (name: string): void => { if (navigationRef.isReady()) { navigationRef.navigate(name); // for "name" => "Argument...

Same for us as in the issue description from @lazyflog. We need enabled `enableHighAccuracy: true` though.

Thanks for the issue! This is indeed affecting our app in production. Is there any hope this will be fixed soon?

Any chance that @iamjon 's [fix](https://github.com/iamjon/react-native-geolocation-service/commit/cad62bd3938136e0d84a73b2a9b465ca9ae2f149) will be released some time soon? We can also confirm the issue with the [current version](https://github.com/Agontuk/react-native-geolocation-service/releases/tag/v5.3.1) of react-native-geolocation-service: * on iOS frequent timeout errors...

~For us this is working fine again (on iOS & Android) even though the supposed [fix](https://github.com/iamjon/react-native-geolocation-service/commit/cad62bd3938136e0d84a73b2a9b465ca9ae2f149) was not merged. Can you confirm @NoahFace ?~

I just edited my comment from Dec last year. It still isn't working propperly for iOS. Any hope that there will be a new version with @iamjon 's PR included...

@Agontuk is this repo still maintained? Any plans on merging this and creating a new version?