Status Update
Comments
ma...@iternio.com <ma...@iternio.com>
sa...@iternio.com <sa...@iternio.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.
jc...@google.com <jc...@google.com>
ab...@google.com <ab...@google.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.
ra...@googlemail.com <ra...@googlemail.com> #4
Seems like a fairly easy fix on our end. I'll see to that it is fixed in 1.5.
li...@google.com <li...@google.com>
ab...@google.com <ab...@google.com>
ab...@google.com <ab...@google.com>
sa...@iternio.com <sa...@iternio.com> #5
in which version is this fixed? I can still see it in 7.5
ab...@google.com <ab...@google.com> #6
The fix will be available in 7.6
sa...@iternio.com <sa...@iternio.com> #7
Android Auto: 7.6.621734-release
ab...@google.com <ab...@google.com>
sa...@iternio.com <sa...@iternio.com> #9
sa...@iternio.com <sa...@iternio.com> #10
je...@google.com <je...@google.com> #11
Looking.
je...@google.com <je...@google.com> #12
Hi Samuel, from my understanding this issue occurred when you tried to set CarIcon in the 'Cue' of the Step, I tested adding the CarIcon in the 'Cue' but didn't see this issue.
ra...@googlemail.com <ra...@googlemail.com> #13
Not in the secondary instruction, it happens in the main instruction.
ra...@googlemail.com <ra...@googlemail.com> #14
Please read the details from the first post, there are also screenshot of where it happens.
ra...@googlemail.com <ra...@googlemail.com> #15
So just to show a sample of the problem again. As you can see in the main instruction the upper and lower part is cut, however in the secondary instruction it is fully visible.
This uses CarIconSpan.ALIGN_CENTER
. If i use bottom or top, it will be moved more to bottom or more to top. Earlier the image was just shrinked to line size.
If multiple lines are shown, the icon normally is fully shown, however it is still larger than the line height. Whole code:
CarIcon roadRefIcon = new CarIcon.Builder(IconCompat.createWithBitmap(bitmap)).build();
CarIconSpan carIconSpan = CarIconSpan.create(roadRefIcon, CarIconSpan.ALIGN_CENTER);
...
SpannableString cueSpan = new SpannableString(cueText);
cueSpan.setSpan(carIconSpan, replaceIndex, REPLACE_WITH_SVG.length() + replaceIndex, Spannable.SPAN_INCLUSIVE_EXCLUSIVE);
instructionStep.setCue(cueSpan);
We did not change any code, stopped working somewhere between Android Auto 7.3 and 7.5.
je...@google.com <je...@google.com> #16
Hi
ra...@googlemail.com <ra...@googlemail.com> #17
No but this is clearly an issue with the android auto app, as the behaviour changed from one version to another. Also there is no stable release version above 1.1.0 yet, so we don't want to update yet.
ra...@googlemail.com <ra...@googlemail.com> #18
Also it was promised to be resolved with 7.6. earlier, so why was that even said if there could be a problem in the car lib?
je...@google.com <je...@google.com> #19
Hi
ra...@googlemail.com <ra...@googlemail.com> #20
I can only see the RC, which is not a release. I just build a new version of our app with that version for testing and will report back here.
ra...@googlemail.com <ra...@googlemail.com> #21
It's still cut off with 1.2.0-rc01.
This should be easily reproducible in the sample app too, so please fix it!
ra...@googlemail.com <ra...@googlemail.com> #22
I just reproduced this in the sample app. In navigation app in DemoScript change step 1 to this:
CarIcon roadRefIcon = new CarIcon.Builder(IconCompat.createWithResource(carContext, R.drawable.circle)).build();
CarIconSpan carIconSpan = CarIconSpan.create(roadRefIcon, CarIconSpan.ALIGN_CENTER);
SpannableString cueSpan = new SpannableString("bla 123");
cueSpan.setSpan(carIconSpan, 0, 1, Spannable.SPAN_INCLUSIVE_EXCLUSIVE);
Step step1 =
new Step.Builder("State Street")
.setManeuver(
getManeuverWithExitNumberAndAngle(
carContext,
Maneuver.TYPE_ROUNDABOUT_ENTER_AND_EXIT_CCW_WITH_ANGLE,
step1IconResourceId,
2,
270))
.setRoad("State Street")
.addLane(straightNormal)
.addLane(straightNormal)
.addLane(straightNormal)
.addLane(straightNormal)
.addLane(rightHighlighted)
.setLanesImage(lanesImage)
.setCue(cueSpan)
.build();
And use the png from here for circle:
ra...@googlemail.com <ra...@googlemail.com> #23
BTW the car app samples repository is also quite messed up, it uses 1.3.0-alpha01 lib stuff but only requires 1.2.0 in build gradle and also the build gradle plugin version with 4.0.1 is wrong as it does not compile. I used 7.0.4. Please also fix the samples repo.
Wrong gralde version
Wrong car lib version:
je...@google.com <je...@google.com> #24
Hi
ra...@googlemail.com <ra...@googlemail.com> #25
Hi,
did you fix this yet? If so in which version it will be available?
je...@google.com <je...@google.com> #26
jc...@google.com <jc...@google.com>
ra...@googlemail.com <ra...@googlemail.com> #27
This is still not fixed in 8.1
ni...@google.com <ni...@google.com> #28
Thanks for reaching out to us. Could you please update the library version as 1.4.0-beta02 and the Android Auto app version and see if it still reproduces?
Thanks,
ra...@googlemail.com <ra...@googlemail.com> #29
It should be fixed by now.
Description
Devices/Android versions reproduced on: AVD "Google Play ARM 64 v8a System Image, API Level 32, Revision 3", Pixel 6 Pro SPA2A.220305.013.A3
Android Auto version reproduced on: 7.5.121304-release.daily
Running the latest available Android Auto Beta makes our CarIcon inside the routing card cut off at the top. See attached screenshot, left is latest AA release (7.3.620524) build from Play Store and right is the latest Beta (7.5.121304).
The Bitmap we use for that has a size of 40x65 and 96dpi.
If this is a bug in the library, we would appreciate if you could attach, if possible:
- Sample project to trigger the issue.
- A screen record or screenshots showing the issue (if UI related).
- A bug report
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Please note, bug report attachments should not be included directly in issue reports.
Disclaimer:
Please note, by submitting a bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
- File names
- Installed apps and usage
- Email addresses of the profiles on the device
- Device identifiers, such as phone number
- Web history information, including URLs / URIs
- Location information, including limited location history
- Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
- System or device information, such as memory and processes