mapbox / mapbox/mapbox-navigation-ios
[Bug]: [Warning, nav-native]: Simulation after location update detected. Simulation for 1.9s
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
### 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning with MapboxNavigation 2.18.4 and MapboxMaps 10.19.0 using the listed stationary, motorcycle-profile navigation steps. Trace where `[Warning, nav-native]: Simulation after location update detected` is emitted and determine whether the behavior is configurable; done means the stationary real-navigation case no longer triggers unwanted simulation or the supported limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100