Open WikkidEdd opened 2 years ago
@WikkidEdd
Hi, Edd. May I have a few questions based on your information?
Thank you very much.
Windows.Perception.Spatial.SpatialAnchorExporter.RequestAccessAsync()
that never returns.@WikkidEdd Hi, Edd. As I mentioned in Issue 356. I spent several attempts to build and run the ASABug app on my HL2, unfortunately I never got a chance to reproduce it successfully.
@WikkidEdd
We just released a new version of SDK 2.13.0. Could you try this new version of SDK to see if the problem still persists please? Thank you very much.
Hello @WikkidEdd - similarly for this issue, was the update in July helpful? If not, please let us know along with any additional details that may be helpful for us to investigate further, thank you
Description We've been experiencing issues in our app where occasionally the ASA setup flow would never return from SpatialAnchorManager.CreateSessionAsync(). We made an editable copy of the ASA Core package so we could add some extra logging in and we tracked the issue down to the call to
Windows.Perception.Spatial.SpatialAnchorExporter.RequestAccessAsync();
which is called when validating the configuration. This function will await forever.It appears to be some kind of race condition or timing-based issue as depending on what Unity version we use, it triggers at a slightly different frequency, going from 10% up to 50% of the time. Furthermore, we can't reproduce it in a standalone test app, only in our own app, but given how constrained the problem function is it's hard to conclude there is something specific in our app which is causing the problem.
As a workaround, we've commented out the spatial perception permission check and we no longer suffer the issue anymore.
We use ASA for synchronising multiple users in the same room, but because we're a distributed team we don't regularly get to test the feature so we can't say for sure when this issue started happening. Anecdotally, our users have reported more issues with ASA recently despite the app in the store not changing for 2 months. It's not conclusive, but it may indicate an OS update that causes this to happen more frequently.
Development information
AR Device information