mapbox / mapbox/mapbox-navigation-android-examples

Historical trajectory replay problem

Open
#214 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
65
Forks
56
Avg merge
1d 4h
Merged PRs (30d)
2

Description

Using v3Demo, the navigation SDK was upgraded to 3.7.0, and an abnormal error was reported when using the historical replay function:
Error log:
java.lang.IllegalStateException: native CUSTOM origin isn't supported
at com.mapbox.navigation.base.internal.utils.RouterExKt.mapToSdkRouteOrigin(RouterEx.kt:22)
at com.mapbox.navigation.core.history.model.HistoryEventMapper.mapNavigationRoutes(HistoryEventMapper.kt:104)
at com.mapbox.navigation.core.history.model.HistoryEventMapper.mapSetRoute(HistoryEventMapper.kt:73)
at com.mapbox.navigation.core.history.model.HistoryEventMapper.map(HistoryEventMapper.kt:41)
at com.mapbox.navigation.core.history.MapboxHistoryReader.loadNext(MapboxHistoryReader.kt:44)
at com.mapbox.navigation.core.history.MapboxHistoryReader.next(MapboxHistoryReader.kt:38)
at com.mapbox.navigation.core.history.MapboxHistoryReader.next(MapboxHistoryReader.kt:13)
at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:210)
at kotlin.sequences.FilteringSequence$iterator$1.calcNext(Sequences.kt:170)
at kotlin.sequences.FilteringSequence$iterator$1.hasNext(Sequences.kt:194)
at kotlin.sequences.SequencesKt___SequencesKt.toCollection(_Sequences.kt:787)
at kotlin.sequences.SequencesKt___SequencesKt.toMutableList(_Sequences.kt:817)
at kotlin.sequences.SequencesKt___SequencesKt.toList(_Sequences.kt:808)
at com.mapbox.navigation.examples.standalone.replay.HistoryFileLoader$loadDefaultReplayHistory$2.invokeSuspend(HistoryFileLoader.kt:50)
at com.mapbox.navigation.examples.standalone.replay.HistoryFileLoader$loadDefaultReplayHistory$2.invoke(Unknown Source:8)
at com.mapbox.navigation.examples.standalone.replay.HistoryFileLoader$loadDefaultReplayHistory$2.invoke(Unknown Source:4)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:89)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:169)
at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:1)
at com.mapbox.navigation.examples.standalone.replay.HistoryFileLoader.loadDefaultReplayHistory(HistoryFileLoader.kt:37)
at com.mapbox.navigation.examples.standalone.replay.HistoryFileLoader$loadReplayHistory$2.invokeSuspend(HistoryFileLoader.kt:25)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@fe0fdc5, Dispatchers.Main.immediate]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the v3Demo historical replay flow and the stack-trace entry points HistoryFileLoader, HistoryEventMapper, and RouterExKt. Reproduce the replay failure with navigation SDK 3.7.0, then trace the CUSTOM origin mapping path; done means historical replay loads without the reported IllegalStateException.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.