expo: Location.watchPositionAsync() - timeInterval option is not working

🐛 Bug Report

Summary of Issue

When using the Location.watchPositionAsync method, if you input a timeInterval option the callback function will never update. If you input both a timeInterval and a distanceInterval it seems like the timeInterval is ignored entirely.

Environment - output of expo diagnostics & the platform(s) you’re targeting

Expo CLI 3.27.4 environment info: System: OS: Windows 10 10.0.18362 Binaries: Node: 10.16.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.19.1 - ~\AppData\Roaming\npm\yarn.CMD npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763 npmPackages: expo: ^38.0.10 => 38.0.10 react: ~16.11.0 => 16.11.0 react-dom: ~16.11.0 => 16.11.0 react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2 react-native-web: ~0.11.7 => 0.11.7 Expo Workflow: managed

Targeting both iOS and Android, tested on iOS 13.5.1.

Reproducible Demo

await Location.watchPositionAsync(
  {
    accuracy: Location.Accuracy.BestForNavigation,
    timeInterval: 1000,
    // distanceInterval: 0,  
   },
  (loc) => {console.log(loc)}
)

Steps to Reproduce

• If you run the above ‘Reproducible Demo’ you should see your app print your location into the console once (or sometimes twice for a possibly unrelated bug) and then never update your location again.
• If you comment out the timeInterval option you should experience the same behaviour.
• If you enable the distanceInterval option you should now experience a regular stream of location updates into your console (the expected behaviour).
• If you enable both the timeInterval and distanceInterval options you should experience the same behaviour as having only the distanceInterval option enabled.
• If you play with the distanceInterval values the option appears to behave as expected.

Expected Behavior vs Actual Behavior

I would expect that when timeInterval is set to 1000 I experience a location update every one second. Instead it seems that the timeInterval option does nothing, behaving the same way as if I had not set the option at all.