-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[expo-location][SDK 50][android] Error: Exception in HostObject::get for prop 'NativeUnimoduleProxy': expo.modules.location.TaskManagerNotFoundException: Could not find the task manager, js engine: hermes #25979
Comments
same issue, did you solve it? |
+1 |
hi there! the |
same issue with expo-location |
hi @Kudo import { getCurrentPositionAsync } from 'expo-location'
getCurrentPositionAsync({}).then(console.log); https://github.com/NervJS/taro-native-shell/tree/v0.73.0-10 |
thanks @zhiqingchen. i can confirm that is a regression issue in sdk 50. |
Thank you for filing this issue! |
same issue |
for me, I installed TaskManger and rebuilt the applications with clearing, good luck |
this worked for me, thanks for sharing! |
…start (#26200) # Why fixes #25979 `expo-task-manager` should only be required by `expo-location` when necessary. After the recent migration to Kotlin it is being required in the `OnCreate` block, which leads to errors in projects without `expo-task-manager` ENG-10952 # How Made the `mTaskManager` variable lazy initialised which means that it will throw an unavailability exception only when used by a method. Also updated the error message. # Test Plan Tested on a physical Android 13 device in BareExpo and a in fresh SDK 50 project without `expo-task-manager`.
…start (#26200) # Why fixes #25979 `expo-task-manager` should only be required by `expo-location` when necessary. After the recent migration to Kotlin it is being required in the `OnCreate` block, which leads to errors in projects without `expo-task-manager` ENG-10952 # How Made the `mTaskManager` variable lazy initialised which means that it will throw an unavailability exception only when used by a method. Also updated the error message. # Test Plan Tested on a physical Android 13 device in BareExpo and a in fresh SDK 50 project without `expo-task-manager`. (cherry picked from commit 8aad587)
…start (expo#26200) # Why fixes expo#25979 `expo-task-manager` should only be required by `expo-location` when necessary. After the recent migration to Kotlin it is being required in the `OnCreate` block, which leads to errors in projects without `expo-task-manager` ENG-10952 # How Made the `mTaskManager` variable lazy initialised which means that it will throw an unavailability exception only when used by a method. Also updated the error message. # Test Plan Tested on a physical Android 13 device in BareExpo and a in fresh SDK 50 project without `expo-task-manager`.
Minimal reproducible example
https://github.com/NervJS/taro-native-shell/tree/v0.73.0-9
Summary
expo-location 16.5.0
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 14.1.2
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.2/bin/yarn
npm: 10.2.4 - ~/.nvm/versions/node/v18.18.2/bin/npm
Watchman: 2023.10.23.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.14.2 - /opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.14.2/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, watchOS 10.2
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10811636
Xcode: 15.1/15C65 - /usr/bin/xcodebuild
npmPackages:
expo: ~50.0.0-preview.4 => 50.0.0-preview.4
react: 18.2.0 => 18.2.0
react-native: 0.73.0 => 0.73.0
Expo Workflow: bare
The text was updated successfully, but these errors were encountered: