Skip to content
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

Closed
zhiqingchen opened this issue Dec 16, 2023 · 10 comments · Fixed by #26200

Comments

@zhiqingchen
Copy link

Minimal reproducible example

https://github.com/NervJS/taro-native-shell/tree/v0.73.0-9

Summary

expo-location 16.5.0

image

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

@zhiqingchen zhiqingchen added the needs validation Issue needs to be validated label Dec 16, 2023
@expo-bot expo-bot added needs review Issue is ready to be reviewed by a maintainer and removed needs validation Issue needs to be validated labels Dec 16, 2023
@SamiAljord
Copy link

same issue, did you solve it?

@b0iq
Copy link

b0iq commented Dec 18, 2023

+1

@Kudo
Copy link
Contributor

Kudo commented Dec 19, 2023

hi there! the NativeModules.NativeUnimoduleProxy is an internal api and has been deprecated. i didn't see your usage for expo-location inside your repro. could you share more details for your usage?

@ngondat97
Copy link

same issue with expo-location

@zhiqingchen
Copy link
Author

hi @Kudo
I just updated the demo.

import { getCurrentPositionAsync } from 'expo-location'
getCurrentPositionAsync({}).then(console.log);

https://github.com/NervJS/taro-native-shell/tree/v0.73.0-10

@Kudo
Copy link
Contributor

Kudo commented Dec 19, 2023

thanks @zhiqingchen. i can confirm that is a regression issue in sdk 50.

@Kudo Kudo added Android Location Issue accepted and removed needs review Issue is ready to be reviewed by a maintainer labels Dec 19, 2023
@expo-bot
Copy link
Collaborator

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.

@thanhloc-17
Copy link

same issue

@mo-fouad
Copy link

for me, I installed TaskManger and rebuilt the applications with clearing,
please check the infoPlist in the config.
https://docs.expo.dev/versions/latest/sdk/task-manager/

good luck

@SamiAljord
Copy link

for me, I installed TaskManger and rebuilt the applications with clearing, please check the infoPlist in the config. https://docs.expo.dev/versions/latest/sdk/task-manager/

good luck

this worked for me, thanks for sharing!

behenate added a commit that referenced this issue Jan 8, 2024
…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`.
behenate added a commit that referenced this issue Jan 8, 2024
…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)
onizam95 pushed a commit to onizam95/expo-av-drm that referenced this issue Jan 15, 2024
…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`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants