As a reminder: WebXR Depth Sensing - is a Draft Spec, read here: https://immersive-web.github.io/depth-sensing/
It means it is not production ready, and should not be used in any production as stated by W3C. It is subject to changes without any guarantees to work.
This means, the API is constantly modified against evolving Specs, and UAs can change it at will, without obligations to make it compatible. Especially since it is not available without chrome://flags WebXR Incubations flag turned on. So if your project suddenly broke, make sure you understand the reasoning for that, either it is due to your code changes, or engine changes, or UA changes.
Also, if your project broke, please share the replication URL, it will help us replicate an issue and work on a fix if it is under our abilities. Currently, I’ve ran WebXR AR Depth Sensing demos in Android Chrome 89, with Incubations flag on, and it does not crash with errors. So this still works: https://playcanv.as/p/UN0z1XE2/
Spec for the WebXR Depth Sensing is changing currently by the W3C team, you can check on progress here: https://github.com/immersive-web/depth-sensing
UAs are updating their latest versions too, so Canary (Chrome 91), is already implemented latest Draft Spec, and PR to PlayCanvas engine that reflects those changes is coming, but during implementation I had concerns with Specs changes, and started discussion on W3C repo regarding spec.