Always Failing HostAnchor about arcore-ios-sdk

[Jacquelinett]

Did you set up Firebase real-time database?

[ramrcram]

@Jacquelinett, Thanks for the reply. Yes, I do set up the firebase real-time database.
Rooms object has been created in firebase. ( Attached screenshot)

[sammcd]

Thanks for checking out the sample project, and sorry you are running into this issue.

It might be worth modifying the sample app's hostCloudAnchor:error: call, to print out the error. Let me know if it gives you anything interesting there.

If it doesn't, the app's - (void)session:(GARSession *)session didFailToHostAnchor:(GARAnchor *)anchor { method you could print out the anchor's cloudState property. Between these two things we should be able to find out exactly what is going wrong.

Thanks!

[ramrcram]

Thanks for the suggestions. Below is the debugging details.
hostCloudAnchor:error: given error as nil.
- (void)session:(GARSession *)session didFailToHostAnchor:(GARAnchor *)anchor cloud state property is GARCloudAnchorStateErrorInternal.

Thanks!

[sammcd]

Sorry this is a pretty tough one to debug on our end. Would you mind giving us your GCP project number (https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)?

This will help us find a little more info on exactly what is going wrong.

Thanks a lot for your patience!

[ramrcram]

Thanks for your effort on this issue.
Here is my GCP number: 85871926483

Thanks!.

[sammcd]

We've looked into this a little on our side.

My best guess is that our API hasn't seen enough ARFrames with a good tracking state to host the anchor.

My best suggestion to mitigate this would be to:

1. Launch the app
2. Make sure you move the app around enough that it is able to locate a plane. We show these in the app in a blue color.
3. Attempt to host the anchor.

My assumption is that step 2) was the missing step. Let me know if this helps. If it doesn't I can look into other reasons this could be happening.

Thanks again for your patience!

[msekast]

I'm seeing an internal error as well, but I'm on xcode 10.0 beta 4/iOS 12 beta.

[ramrcram]

@msekast I'm too on Xcode 10.0 beta 4/iOS 12 beta.
@sammcd, No luck :( I have tried your suggestion but still am getting an internal error.

[sammcd]

Thanks for the additional info! I apologize for not asking sooner if you are on the current iOS beta.

We have a bug that is fixed in the next release (1.4) that causes this issue on iOS 12. We should be launching this fix within a week. I will update this thread when I release that version. If you would like to continue testing it might be helpful to test on an iOS 11 device until we get this fix out.

[ramrcram]

Cool thanks @sammcd. My bad I should have mention iOS version in the first place. :(.
Thanks for taking care, Waiting for the new release. 👍

[sammcd]

We recently released 1.4.0 which includes this fix. Update your podfile to 1.4.0 and run pod install --repo-update. This should solve your issue. If it doesn't, or if you run into anything else please let me know!

[ramrcram]

👍