When using pure ARKit we ask the user to move their device around to establish tracking. We respond to these status changes with session:cameraDidChangeTrackingState. In my experience usually takes at least 5-10 seconds to establish solid tracking.
I'm working on a project in Unity using Vuforia vumark targets to localize to a physical space but the experience relies heavily on extended tracking. My belief is that with Vuforia 7.2.# this extended tracking should be managed through ARKit.
So I have my project configured for position device tracking optimized for Image Targets and VuMarks. I am responding to tracking status using
What's happening is that almost instantly I'm getting a callback with TrackableBehavior.Status = 'Tracked' and TrackableBehavior.StatusInfo = 'normal'.
The speed at which this is returned leads me to believe that this callback is not truly reporting on ARKits tracking status, and if I start the experience too quickly tracking does not seem as stable initially.
How can I ensure solid ARKit tracking status before instructing my user's to find the vumark to start the experience?