-
Notifications
You must be signed in to change notification settings - Fork 88
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
Error when resolving anchors. No callback received. #100
Comments
Hi Vishal, can you provide a minimum reproducible sample project? Also, do you see the same behavior when using the asynchronous APIs e.g. https://developers.google.com/ar/reference/ios/category/GARSession(CloudAnchors)#resolvecloudanchorwithidentifier:completionhandler:error: |
Sample.zip |
Is this issue related to google-ar/arcore-unity-extensions#56, cloud anchors not hosting when TTL = 365? |
No. It's not. It is regarding slow resolving and sometimes not resolving in case of multiple anchor resolving request simultaneously. |
Also receiving the following state for anchors: |
We are having an AR application which saves the cloud anchor ids in the backend and then retrieves it & tries to resolve the anchor.
private func resolvedAnchors() {
guard let deviceLastLocation = deviceLastLocation else { return }
and I don't get any failure callbacks in didFailToResolve but sometimes when it is able to fetch the anchor I do receive didResolve callback.
Used to work fine like a month ago. Suddenly the resolving is taking too long & fails to resolve multiple calls.
The text was updated successfully, but these errors were encountered: