Status Update
Comments
ra...@googlemail.com <ra...@googlemail.com> #2
Any updates on this? It's been a month already since I reported it, and it seems this crash is occurring quite frequently for my users.
ja...@iternio.com <ja...@iternio.com> #3
I am still regularly receiving reports about this issue, and it seems it has not been addressed in the latest 1.4.0-rc01 release.
ju...@kakaomobility.com <ju...@kakaomobility.com> #4
Seems like a fairly easy fix on our end. I'll see to that it is fixed in 1.5.
ca...@google.com <ca...@google.com>
ra...@googlemail.com <ra...@googlemail.com> #5
Could you please provide some feedback on this? This is a very annoying bug, when you start driving and you want to know where to go, but the route can not be started...
As the initial link doesn't work anymore please check this video:
ra...@googlemail.com <ra...@googlemail.com> #6
I can reproduce that on any AA app there is, here as a sample with TomTom Amigo:
So it's not related to any specific app, it's an AA bug.
Description
Devices/Android versions reproduced on: Pixel 6, Pixel 3
Android Auto version reproduced on: every version from roughly 9 onwards
I made a video of the problem:
To quickly summarize the issue:
When the car is parked (P gear), everything works as expected. When in drive mode (D gear), the additional loading spinner is suddenly shown.
This does not only happen to our own app, but i could reproduce it with other apps, like TomTom Amigo too. Also it is reproducible in the sample app. It can be reproduced in DHU as well, when changing this flag:
```
Driving Restrictions:
"restrict none" "restrict all"
```
none equals gear P
restrict all equals gear D
This is very annoying, as there is no obvious reason, why the loading indicator is shown. This was introduced somewhere beginning of this year. Before it worked properly.
Please fix!