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

Hit test takes a long time to get ready #72

Closed
killerfrienddk opened this issue May 1, 2020 · 2 comments
Closed

Hit test takes a long time to get ready #72

killerfrienddk opened this issue May 1, 2020 · 2 comments

Comments

@killerfrienddk
Copy link

Title, i do not know what is wrong but it can take up to 2-3 mins for it to start working.
Using a samsung galaxy 7

@bialpio
Copy link
Contributor

bialpio commented May 1, 2020

This certainly does not seem right. Can you provide more details about the behavior that you are seeing? Is this a hit test subscription promise that takes a long time to resolve but then the results are available (& non-empty in subsequent frames), or are the results consistently empty (but the promise resolves quickly), or both? Are there any error messages in the console?

@killerfrienddk
Copy link
Author

This certainly does not seem right. Can you provide more details about the behavior that you are seeing? Is this a hit test subscription promise that takes a long time to resolve but then the results are available (& non-empty in subsequent frames), or are the results consistently empty (but the promise resolves quickly), or both? Are there any error messages in the console?

Seems like it was my carpet that was bad for tracking, kinda weird since most other trackers i have tested worked fine on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants