Local serialization for lost connectivity?

[lmaxsmith]

My app is used in is settings where connectivity is sparse. I want to share anchors when available, but store copies locally for instances when no connectivity is available. First question: is this something that is possible by default and I just missed it? Second question: When I tried to implement my own logic for it, ASA seemed to prevent it because it took over the AR Anchor Manager's behavior so my local anchors wouldn't work.

What am I missing?

[Varnauld]

Hello, thank you for reaching out - tagging @XiangyuL-Microsoft to help here (tracking ID 41668537)

[XiangyuL-Microsoft]

@lmaxsmith To persistent the anchors, all of them should be stored in Azure. You can try to temporarily cache some anchors, but it is not a recommended solution for now by design. The recommended way is detecting network status and provide real-time function only when the network is available.

Could you please share with us about the detail how ASA prevent you implement your own logic? For example, do you have any sample code?

@Varnauld I would like to consider the local anchor serialization w/o network connectivity as a feature request. How about discuss with engineering team to see if we would provide it in our incoming new SDK?

[mrwellmann]

I haven't thought in depth about this but local anchor serialization w/o network connectivity might also make it possible to do more easy or even automatic testing utilizing Unity Mars.

[Varnauld]

Hello @lmaxsmith - following up on this issue, were you able to resolve or do you have any follow up questions? @XiangyuL-Microsoft mentioned that you might have a feature request to share with the team, if so, please do share here thank you!

[lmaxsmith]

No, ASA had too many problems for my implementation so I tabled it. Working with other anchoring for now.