Bug P2
Status Update
No update yet.
Comments
so...@gmail.com
As a workaround we added the following to our own manifest:
<provider
tools:replace="android:authorities"
android:name="com.google.android.gms.measurement.AppMeasurementContentProvider"
android:authorities="${applicationId}.google_measurement_service"
android:exported="false" />
You must have tools namespace defined in the xml.
<provider
tools:replace="android:authorities"
android:name="com.google.android.gms.measurement.AppMeasurementContentProvider"
android:authorities="${applicationId}.google_measurement_service"
android:exported="false" />
You must have tools namespace defined in the xml.
so...@gmail.com
I've also been affected by this!
so...@gmail.com
@2 I also opened an issue with tools guys https://code.google.com/p/android/issues/detail?id=193567 . I'm not really sure which team should fix it. There's another workaround there that in my opinion is cleaner.
Description
When did this happen?
October 6, 2019 10:08 AM GMT-05:00
What steps would let us observe this issue?
1. Using Android Audio connected to Jeep Gladiator via USB-C
2. Initiate phone call
What did you expect to happen?
Phone call would be routed to car's audio system
What actually happened?
Android Auto routed the phone call to the handset rather than the car's audio system. To make matters worse, while Android Auto is connected the phone UI is unavailable so it can't be changed from the handset to the vehicle.
How often has this happened?
Frequently
Additional comments
Have reported this previously (