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

Clarified lifecycle of ARSession along with ARCoreExtensions #223

Open
t5ujiri opened this issue Nov 21, 2024 · 0 comments
Open

Clarified lifecycle of ARSession along with ARCoreExtensions #223

t5ujiri opened this issue Nov 21, 2024 · 0 comments

Comments

@t5ujiri
Copy link

t5ujiri commented Nov 21, 2024

During development using the ARCore Unity Extension, inconvenience arises from not knowing when an ARCore Session is initialized and configured for authentication.

For example, in iOS, the API can be successfully called by activating the game object in XROrigin/ARSession/ARCoreExtensions that has been previously deactivated with the Start function and then setting SetAuthToken (however but there is a problem with the session not being set correctly immediately after the app is installed #76 ).
On the other hand, on Android, Keyless Authentication will not work correctly if the GameObject is disabled on the scene as described above.

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

1 participant