Cristiano Coelho

@satya164 any insights on this? This is still a problem, and using a custom theme does not resolve the issue. The only work around is to use the native navigator,...

This is still a release blocker to migrate from 5.x to 6.x. I guess the non-native stack navigators aren't really maintained or supported any more?

Still a release blocker, @kacperkapusciak is there any reason this hasn't been looked into yet? Is the non-native navigator no longer supported?

Still a problem.

Almost one year and this is still broken.

Just a little update about what the issue is: Let's say we want to call getCurrentPosition to be precise (and without significant location), but we also want to monitor location...

I've tried to tackle the issue in this PR (https://github.com/react-native-community/react-native-geolocation/pull/88) by using 2 managers instead of 2; one for the watcher and one for getCurrentPosition. For my use-case it is...

Any reviews? Thoughts? Possible caveats?

Hi @michalchudziak , I actually switched to https://github.com/Agontuk/react-native-geolocation-service which proved to be much more reliable and customizable.

After further testing (and unlinking), I noticed that linking is not needed. The library works fine without linking. Can anyone confirm? Was I just luck due to link + unlink?