Our AR core install flow assumes that ResumeTracking will be called after ArCore has either been updated/installed or the update/install request was cancelled (see [1]). However, ResumeTracking is not called in that case. As a result, we queue up some AR session requests and never answer them. Also, reloading the page in that causes the following crash:

[FATAL:isolated_xr_service.mojom.cc(1069)] Check failed: !connected. XRRuntime::RequestSessionCallback was destroyed without first either b
eing run or its corresponding binding being closed. It is an error to drop response callbacks which still correspond to an open interface pipe.

[1] https://cs.chromium.org/chromium/src/chrome/browser/android/vr/arcore_device/arcore_device.cc?rcl=cb66a54e60d13ab0593e3b387f8f90b0ddd43e8b&l=113