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

Error when resolving anchors. No callback received. #100

Open
vishal219 opened this issue Apr 18, 2024 · 5 comments
Open

Error when resolving anchors. No callback received. #100

vishal219 opened this issue Apr 18, 2024 · 5 comments

Comments

@vishal219
Copy link

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 }

    self.mementosVM.getAllMementos().forEach {[weak self] memento in
        guard let self = self else { return }
        
        if let anchorId:String = memento.anchor_id {
            printObj("AnchorId: "+anchorId)
            
            self.googleSession?.resolveCloudAnchor(anchorId: anchorId)
        }
    }
}

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.

@15kingben
Copy link

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:

@vishal219
Copy link
Author

Sample.zip
@15kingben
Here is the sample app. You will need to add your google-info.plist and api key. I have used local storage (UserDefaults for anchor Ids) in this.

@15kingben
Copy link

Is this issue related to google-ar/arcore-unity-extensions#56, cloud anchors not hosting when TTL = 365?

@vishal219
Copy link
Author

No. It's not. It is regarding slow resolving and sometimes not resolving in case of multiple anchor resolving request simultaneously.

@vishal219
Copy link
Author

Also receiving the following state for anchors: GARCloudAnchorStateErrorInternal in the callback

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