You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is expected behavior, but when calling start and then calling getCurrentPosition, made getCurrentPosition take 30-60 seconds to resolve. Moving the start call to be after getCurrentPosition, made it resolve instantly.
This was not an issue in version 4.12.1, it was added right after that. It's also only an issue on iOS, android always resolves right away.
Actual Behavior
I would think that it wouldn't matter if start was called before getCurrentPosition, and that it wouldn't result in additional load time.
Steps to Reproduce
Context
Debug logs
Logs
PASTE_YOUR_LOGS_HERE
The text was updated successfully, but these errors were encountered:
I strongly doubt calling .getCurrentPosition before or after .start() has any different behaviour. It is likely a coincidence. Are you testing outdoors?
Also, the first thing to do when something unusual occurs (before posting an issue) is to carefully observe the plug-in logs with your app launched in XCode.
Your Environment
react-native -v
): 0.72.14Expected Behavior
I'm not sure if this is expected behavior, but when calling start and then calling getCurrentPosition, made getCurrentPosition take 30-60 seconds to resolve. Moving the start call to be after getCurrentPosition, made it resolve instantly.
This was not an issue in version 4.12.1, it was added right after that. It's also only an issue on iOS, android always resolves right away.
Actual Behavior
I would think that it wouldn't matter if start was called before getCurrentPosition, and that it wouldn't result in additional load time.
Steps to Reproduce
Context
Debug logs
Logs
The text was updated successfully, but these errors were encountered: