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
Did you reproduce this issue in a development build?
Yes
Summary
Using expo sdk 48 and task manager the background location updates occur with an unexpected frequency.
The location updates are working well when the app is on foreground (log every 1second) but when the app is on background the updates are less frequents (log every 10min - 20min).
Doing the exact same thing with expo sdk50 I can observe that the updates are working well both foreground and background (log every 1 seconds).
Current package.json: "expo": "48.0.0", "react": "18.2.0", "react-native": "0.71.14", "expo-task-manager": "~11.1.1", "expo-location": "~15.1.1"
The implementation seems the one given in basic Taskmanager documentation https://docs.expo.dev/versions/v48.0.0/sdk/task-manager/
As I am not able to upgrade to sdk 50 yet, Is it a known issue with startLocationUpdatesAsync ? is there a workaround ? Or maybe I am doing something wrong ?
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
The text was updated successfully, but these errors were encountered:
Minimal reproducible example
https://github.com/vincentgrassin/expo-sdk48-taskmanager
What platform(s) does this occur on?
Android
Did you reproduce this issue in a development build?
Yes
Summary
Using expo sdk 48 and task manager the background location updates occur with an unexpected frequency.
The location updates are working well when the app is on foreground (log every 1second) but when the app is on background the updates are less frequents (log every 10min - 20min).
Doing the exact same thing with expo sdk50 I can observe that the updates are working well both foreground and background (log every 1 seconds).
Current package.json:
"expo": "48.0.0", "react": "18.2.0", "react-native": "0.71.14", "expo-task-manager": "~11.1.1", "expo-location": "~15.1.1"
The implementation seems the one given in basic Taskmanager documentation https://docs.expo.dev/versions/v48.0.0/sdk/task-manager/
As I am not able to upgrade to sdk 50 yet, Is it a known issue with
startLocationUpdatesAsync
? is there a workaround ? Or maybe I am doing something wrong ?Thanks in advance
Environment
expo-env-info 1.2.0 environment info:
System:
OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
Yarn: 1.22.21 - ~/Documents/dev/sandbox/node_modules/.bin/yarn
npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
npmPackages:
expo: 48.0.0 => 48.0.0
react: 18.2.0 => 18.2.0
react-native: 0.71.14 => 0.71.14
npmGlobalPackages:
eas-cli: 3.8.0
expo-cli: 6.3.10
Expo Workflow: managed
Expo Doctor Diagnostics
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
The text was updated successfully, but these errors were encountered: