[Bug]: LocationMatching return delay, time uncertain

Mapbox Navigation SDK version

The version of Mapbox I am using is Map: 11.25.0, Navigation: 3.25.0, Search: 2.25.0

Steps to reproduce

The version of Mapbox I am using is Map: 11.25.0, Navigation: 3.25.0, Search: 2.25.0. After initiating real navigation, I found that self. mapboxNavigation? .navigation().routeProgress
.sink { status in
let matching = self.mapboxNavigation? .navigation().currentLocationMatching
print("routeProgress: (status != nil), locationMatching: (matching != nil)")
// . ..
}The callback surface of. store (in:&cancellable) will show that after real navigation is enabled, locationMatching is nil. After a period of time (time is not fixed, a few seconds for fast navigation and a few minutes for slow navigation), it returns a value. Is this related to GPS positioning? Or is it related to the internet? Is there any way to deal with this return delay?

Expected behavior

The version of Mapbox I am using is Map: 11.25.0, Navigation: 3.25.0, Search: 2.25.0. After initiating real navigation, I found that self. mapboxNavigation? .navigation().routeProgress
.sink { status in
let matching = self.mapboxNavigation? .navigation().currentLocationMatching
print("routeProgress: (status != nil), locationMatching: (matching != nil)")
// . ..
}The callback surface of. store (in:&cancellable) will show that after real navigation is enabled, locationMatching is nil. After a period of time (time is not fixed, a few seconds for fast navigation and a few minutes for slow navigation), it returns a value. Is this related to GPS positioning? Or is it related to the internet? Is there any way to deal with this return delay?

Actual behavior

The version of Mapbox I am using is Map: 11.25.0, Navigation: 3.25.0, Search: 2.25.0. After initiating real navigation, I found that self. mapboxNavigation? .navigation().routeProgress
.sink { status in
let matching = self.mapboxNavigation? .navigation().currentLocationMatching
print("routeProgress: (status != nil), locationMatching: (matching != nil)")
// . ..
}The callback surface of. store (in:&cancellable) will show that after real navigation is enabled, locationMatching is nil. After a period of time (time is not fixed, a few seconds for fast navigation and a few minutes for slow navigation), it returns a value. Is this related to GPS positioning? Or is it related to the internet? Is there any way to deal with this return delay?

Is this a one-time issue or a repeatable issue?

one-time

Start with the routeProgress Combine subscription and currentLocationMatching in the navigation API, using the reported Mapbox Map 11.25.0, Navigation 3.25.0, and Search 2.25.0 versions. Reproduce the delay during real navigation while checking whether GPS positioning or internet connectivity affects it. Done means the cause and expected behavior are established, with a documented or verified way to handle the initial nil value.