Skip to main content
Version: 1.9.0

State

VLSDK internally operates with the following states. Initially, it starts in the INITIAL state, and the state changes based on VL's operations. When the state changes, the OnStateChanged(TrackerState) event of VLSDKManager is triggered.

StateDescription
INITIALThe state where VL is not initialized. This occurs when the app is first launched or when VL requests fail a certain number of times. VL requests are sent according to the interval set in the Request Interval Before Localization of VL Settings. When this state is reached, the AR Session Origin resets to the origin, and all internal VL sessions are initialized.
NOT_RECOGNIZEDThe state where VL requests continuously fail from the INITIAL state.
VL_PASSThe state where a successful VL response is received and internal processing is completed. VL requests are sent according to the interval set in the Request Interval After Localization.
VL_FAILThe state where VL responses are temporarily failing. VL requests are sent according to the interval set in the Request Interval Before Localization. The AR Session Origin updated through VL requests is maintained. If this state persists, it transitions to the INITIAL state.
VL_OUT_OF_SERVICEThe state where no valid VL API can be found using GPS Guide. It continuously searches for a usable VL API using GPS values.

vlsdk_state