mapbox / mapbox/mapbox-navigation-android
Android - DropInUi Crash issues
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Hello Mapbox team,
I am using DropInUI sdk in our app and I am getting two different crashes.
The below one is first crash happening at least 10 times a day.
Fatal Exception: java.lang.IllegalArgumentException: Parse error at offset 638: Missing a colon after a name of object member.
at com.mapbox.common.EventsService.sendEvent(SourceFile)
at com.mapbox.navigation.metrics.MapboxMetricsReporter.addEvent(MapboxMetricsReporter.java:63)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.sendEvent(MapboxNavigationTelemetry.java:34)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.createFreeDriveEvent(MapboxNavigationTelemetry.java:49)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.access$createFreeDriveEvent(MapboxNavigationTelemetry.java)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry$trackFreeDrive$1.invoke(:9)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry$trackFreeDrive$1.invoke(:2)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.ifTelemetryRunning(MapboxNavigationTelemetry.java:12)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.trackFreeDrive(MapboxNavigationTelemetry.java:16)
at com.mapbox.navigation.core.telemetry.MapboxNavigationTelemetry.navigationSessionStateObserver$lambda-2(MapboxNavigationTelemetry.java:74)
at com.mapbox.navigation.core.trip.session.NavigationSession.setState$libnavigation_core_release(:34)
at com.mapbox.navigation.core.trip.session.NavigationSession.updateState(:10)
at com.mapbox.navigation.core.trip.session.NavigationSession.setHasRoutes(:6)
at com.mapbox.navigation.core.trip.session.NavigationSession.onRoutesChanged(:15)
at com.mapbox.navigation.core.directions.session.MapboxDirectionsSession.setNavigationRoutesFinished(:85)
at com.mapbox.navigation.core.MapboxNavigation$internalSetNavigationRoutes$2.invokeSuspend(MapboxNavigation.java:2)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(BaseContinuationImpl.java:14)
at kotlinx.coroutines.DispatchedTaskKt.resume(DispatchedTask.kt:47)
at kotlinx.coroutines.DispatchedTaskKt.resumeUnconfined(DispatchedTask.kt:105)
at kotlinx.coroutines.DispatchedTaskKt.dispatch(DispatchedTask.kt:105)
at kotlinx.coroutines.CancellableContinuationImpl.dispatchResume(CancellableContinuationImpl.java:105)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl(CancellableContinuationImpl.java:45)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl$default(CancellableContinuationImpl.java:17)
at kotlinx.coroutines.CancellableContinuationImpl.resumeWith(CancellableContinuationImpl.java:17)
at com.mapbox.navigation.navigator.internal.MapboxNativeNavigatorImpl$setRoutes$2$2.run(:12)
at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
at android.os.MessageQueue.next(MessageQueue.java:335)
at android.os.Looper.loopOnce(Looper.java:161)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7916)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:577)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)
The below one is second crash which happens twice or thrice a day.
Fatal Exception: java.lang.NullPointerException: Missing required view with ID: app.abcourier.ccmobile:id/maneuverView
at com.mapbox.navigation.dropin.databinding.MapboxManeuverGuidanceLayoutBinding.bind(:32)
at com.mapbox.navigation.dropin.maneuver.ManeuverViewBinder.bind(:18)
at com.mapbox.navigation.dropin.maneuver.ManeuverViewBinder.bind(:2)
at com.mapbox.navigation.ui.base.lifecycle.UICoordinator$onAttached$1$invokeSuspend$$inlined$collect$1.emit(UICoordinator.java:23)
at kotlinx.coroutines.flow.FlowKt__ZipKt$combine$$inlined$combineUnsafe$FlowKt__ZipKt$1$2.invokeSuspend(FlowKt__Zip.kt:63)
at kotlinx.coroutines.flow.FlowKt__ZipKt$combine$$inlined$combineUnsafe$FlowKt__ZipKt$1$2.invoke(FlowKt__Zip.kt:20)
at kotlinx.coroutines.flow.FlowKt__ZipKt$combine$$inlined$combineUnsafe$FlowKt__ZipKt$1$2.invoke(FlowKt__Zip.kt:20)
at kotlinx.coroutines.flow.internal.CombineKt$combineInternal$2.invokeSuspend(Combine.kt:258)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(BaseContinuationImpl.java:14)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.java:100)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7916)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:577)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)
Please check these error reports and let me know how do we solve this issue.
**Android API:32**
implementation 'com.mapbox.navigation:ui-app:2.15.1
implementation 'com.mapbox.navigation:ui-dropin:2.15.1'
Currently I don't have the steps to reproduce the issue.
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 with the two stack traces at MapboxMetricsReporter/MapboxNavigationTelemetry and ManeuverViewBinder, using the reported ui-app and ui-dropin 2.15.1 dependencies and Android API 32. Investigate how each failure is reached, then seek reproduction steps for both crashes. Done means identifying and fixing both failures with verification, although the issue currently provides no reproduction steps or named tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100