mapbox-navigation-ios icon indicating copy to clipboard operation
mapbox-navigation-ios copied to clipboard

[Bug]: [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s

Open xiaoxin3838438 opened this issue 7 months ago • 2 comments

Mapbox Navigation SDK version

2.18.4

Steps to reproduce

  1. 选择一个地点进行真实导航
  2. 规划路线时选择的机动车类型为摩托车类型(driving-traffic)
  3. 保持当前位置不动即可

Test Steps to Reproduce:

Select a destination to initiate real navigation When planning the route, choose "motorcycle" as the vehicle type (driving-traffic profile) Remain stationary at current location (do not move)

Expected behavior

软件版本: pod 'MapboxMaps', '10.19.0' pod 'MapboxNavigation', '2.18.4' pod 'MapboxGeocoder.swift', '0.15.0'

问题: 当我开始真实导航时,我一直静止不动,mapboxSDK 会一直会尝试自动模拟导航,这种情况我该怎么避免 我能设置属性关闭这种现象吗? 如果不行的话,在哪个版本可以关闭这种现象? 如果没有,未来会推出该功能吗? 据测试同事反馈, 安卓SDK不会有这种问题

Software Versions:

ruby pod 'MapboxMaps', '10.19.0' pod 'MapboxNavigation', '2.18.4' pod 'MapboxGeocoder.swift', '0.15.0' Issue Description: When initiating real navigation, my position remains static but the Mapbox SDK keeps attempting automatic simulation. How can I disable this behavior? Specifically:

Is there a configurable property to turn off this auto-simulation feature? If not available in current versions, in which SDK version can this be disabled? If no such version exists, are there plans to implement this control in future releases? Note: Our testing team confirms this issue doesn't occur in the Android SDK.

Actual behavior

Log Output:

[Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s

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

one-time

xiaoxin3838438 avatar Jul 18 '25 05:07 xiaoxin3838438

会出现多次,上面选项选错了 It will appear multiple times, the above option is wrong

xiaoxin3838438 avatar Jul 18 '25 06:07 xiaoxin3838438

Hi folks,

Sorry for the delay with the answer and thank you for your request. Unfortunately we were not able to reproduce the issue on our end, however Navigation SDK internally has the route simulation behavior in the context of poor or missing GPS signal and it's enabled for mobile SDK. The configuration for that is not available from the public interface (it's this noSignalSimulationEnabled parameter).

If it's applicable for you could you please check (the option is to use the local changes) the behavior with noSignalSimulationEnabled: false in your environment.

Thank you!

Cheers, Artem

ArtemStepuk avatar Jul 29 '25 13:07 ArtemStepuk