Assigned
Status Update
Comments
ca...@google.com <ca...@google.com> #2
Yes please :) Along with a more specific definition of how the Popular Times are determined (how much history? done by mobile device activity? check ins?)
ca...@google.com <ca...@google.com> #3
Making popular times available by day of the week would be awesome
ac...@roadie.com <ac...@roadie.com> #4
It already is Jeffrey, you can toggle by day on mobile or desktop
ac...@roadie.com <ac...@roadie.com> #5
Hi,
Following up again—we recently updated to version 6.0.2 after reading in the 6.0.1 release notes that a race condition crash had been resolved. The description closely matched the issue we reported here, so we were hopeful the update would fix it. Unfortunately, we’re still experiencing the same crash.
Could you provide any insights or guidance on this?
Thanks,
Andrew
Following up again—we recently updated to version 6.0.2 after reading in the 6.0.1 release notes that a race condition crash had been resolved. The description closely matched the issue we reported here, so we were hopeful the update would fix it. Unfortunately, we’re still experiencing the same crash.
Could you provide any insights or guidance on this?
Thanks,
Andrew
ca...@google.com <ca...@google.com> #6
@r22, I think Jeff is referring to the ability to split popular times by day of week in the information released by the API, not the currently existing web GUI.
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
Maybe the info appears as a nested object? e.g. "popular times" > "day of week" > "hour of day" > traffic count
Description
===========================================================================================
I’m reaching out regarding an issue I’ve encountered while using the com.google.android.libraries.navigation:navigation:5.5.2 library.
The error in question appears to be a Fatal Exception: java.lang.IllegalStateException: Task was cancelled, and it occurs under circumstances that I haven’t been able to definitively isolate. Below is the stack trace for reference:
Fatal Exception: java.lang.IllegalStateException: Task was cancelled.
at com.google.android.libraries.navigation.internal.rc.a.a(PG:1)
at com.google.android.libraries.navigation.internal.zk.at.run(PG:4)
at android.os.Handler.handleCallback(Handler.java:984)
at android.os.Handler.dispatchMessage(Handler.java:104)
at android.os.Looper.loopOnce(Looper.java:238)
at android.os.Looper.loop(Looper.java:357)
at android.app.ActivityThread.main(ActivityThread.java:8194)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:957)
I suspect the issue could originate from one of three possible areas, but even when I wrap the suspected code in a try-catch block, the application still crashes. At this point, I’m unable to determine the root cause and was hoping you might provide some insights or suggestions on how to proceed. The three areas I would assume would be
1. mPendingRoute?.cancel(true)
2. Waypoint.builder().setLatLng(lat, lng).build()
3. mNavigatior?.currentTimeAndDistance
Here is the code that I'm calling the waypoint builder
mRoutingOptions = RoutingOptions()
mRoutingOptions?.let { routingOptions ->
routingOptions.travelMode(RoutingOptions.TravelMode.DRIVING)
val destination: Waypoint = try {
Waypoint.builder().setLatLng(lat, lng).build()
} catch (e: Waypoint.UnsupportedPlaceIdException) {
Log.e("EstimatedTimeArrivalRepository", "UnsupportedPlaceIdException")
sendEvent()
return
}
Here is where I mPendingRoute cancel
etaJob?.cancel()
mNavigator?.stopGuidance()
mNavigator ?: return
try {
mPendingRoute?.cancel(true)
} catch (e: Exception) {
Log.e("NavigationRepository", "cancel pending route with exception: ${e.message}")
} finally {
mPendingRoute = null
}
This is when I'm calling the the currentTimeAndDistance method
mNavigator?.let {
val timeAndDistance = it.currentTimeAndDistance
}