Location.startLocationUpdatesAsync task callback does not receive any location updates on Android

[Bashin]

Minimal reproducible example

https://github.com/santibernas/expo-issue-28767

What platform(s) does this occur on?

Android

Did you reproduce this issue in a development build?

Yes

Summary

When using Location.startLocationUpdatesAsync to register a TaskManager task the task is registered successfully (verified by TaskManager.getRegisteredTasksAsync) but the callback does not ever get called with location data or even an error on Android.

Here are some Logcat insights.

Initially:
Registered task with name 'LocationTask' for app with scoping identifier 'test.app'.

Thereafter every second:
Handling intent with task name 'LocationTask' and app scoping identifier 'test.app'.
Handling job with task name 'LocationTask' for app with scoping identifier 'test.app'.

After a few minutes (usually less than 15) the app runs out of memory and restarts.

On IOS everything works fine and in SDK 50 with the respective package versions of expo-task-manager and expo-location everything was working on Android as well.

Environment

expo-env-info 1.2.0 environment info:
System:
OS: Windows 11 10.0.22631
Binaries:
Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
Yarn: 3.6.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-233.14808.21.2331.11709847
npmPackages:
expo: ~51.0.8 => 51.0.8
react: 18.2.0 => 18.2.0
react-native: 0.74.1 => 0.74.1
Expo Workflow: bare

Expo Doctor Diagnostics

WARNING: We recommend using PowerShell or Bash via WSL 2 for development with Expo CLI on Windows. You may encounter issues using cmd.exe.

✔ 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 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
✔ Check that packages match versions required by installed Expo SDK

Didn't find any issues with the project!

[Bashin]

Please also note the same problem being reported in the comments of this issue:
#28767

This issue was created on request of @brentvatne and the sample app is by @santibernas

[shuo-hiwintech]

Same question.

[behenate]

@Bashin Hi, are you using the new architecture? Also does the location never work for you or only on the first launch like in this issue? #26373

[Bashin]

Hi @behenate I am not using the new architecture and I have no issues at all on iOS (unlike the issue you mentioned). However, I am unable to receive any location on Android, neither in a dev build nor in production.

[fbinz]

Can also confirm. Position updates are processed on SDK 50, but not on 51.
Regarding the new architecture: The documentation suggests that the expo-location is not supported, so I'm not using it ofc: https://docs.expo.dev/guides/new-architecture/#troubleshooting

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[tknuts]

Prioritize based on severity :-) All Android devices on SDK 51, can't use Location services.

[behenate]

@tknuts It's a major issue, we'll resolve it asap 🫡

[managervcf]

+1

[behenate]

Issue fixed in the PR above, after we merge it will be published under SDK 51 in a few days (probably sometime after App.js)