Verified
Status Update
No update yet.
Comments
am...@google.com
am...@google.com
Thank you for posting.
Kindly provide a sample app with screen recording and steps to reproduce for further checking.
yb...@google.com
ta...@gmail.com
Thank for your help.
The issue is easily reproduced with the Stroke and Width settings for Buildings (3d and Footprint) within the latest Maps JavaScript API and both the old web-based Map Styles editor and the new cloud-based Map Styles editor. You can reproduce the issue by attempting to add an outline (stroke) of any width under Landscape-Human-made(man_made)-Buildings. The expected changes do not show in the rendered map within the Styles editor(s) or when loading the map via saved Map ID elsewhere.
I don't have time this week to author a screen recording that redacts my proprietary intellectual property, and I certainly won't be providing a copy of my software or authoring a sample app for you when you can already easily duplicate the bug in your own Map Styles editors.
I may have time to provide a marked-up screenshot from the Map Styles editor later tonight or tomorrow when I am back at my computer.
The issue is easily reproduced with the Stroke and Width settings for Buildings (3d and Footprint) within the latest Maps JavaScript API and both the old web-based Map Styles editor and the new cloud-based Map Styles editor. You can reproduce the issue by attempting to add an outline (stroke) of any width under Landscape-Human-made(man_made)-Buildings. The expected changes do not show in the rendered map within the Styles editor(s) or when loading the map via saved Map ID elsewhere.
I don't have time this week to author a screen recording that redacts my proprietary intellectual property, and I certainly won't be providing a copy of my software or authoring a sample app for you when you can already easily duplicate the bug in your own Map Styles editors.
I may have time to provide a marked-up screenshot from the Map Styles editor later tonight or tomorrow when I am back at my computer.
am...@google.com
Good morning,
To follow-up on this in an effort to assist you in bringing this bug to a resolution, please see the attached screenshot from the (old) Map Styles editor showing the issue and how you can duplicate it on your own. Similarly, the issue can also be duplicated in the (new) preview of the cloud-based Map Styles editor. Stroke color and width are not working as expected, for both the 3d and footprint style of buildings on the map. To assist you in locating the Map Styles editor, here is the link to Map Styles:https://console.cloud.google.com/google/maps-apis/studio/styles
To follow-up on this in an effort to assist you in bringing this bug to a resolution, please see the attached screenshot from the (old) Map Styles editor showing the issue and how you can duplicate it on your own. Similarly, the issue can also be duplicated in the (new) preview of the cloud-based Map Styles editor. Stroke color and width are not working as expected, for both the 3d and footprint style of buildings on the map. To assist you in locating the Map Styles editor, here is the link to Map Styles:
go...@gmail.com
Thank you for the information.
We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
go...@gmail.com
Thank you for the update and for your help on this. I have stared this issue and will be watching for future updates.
ta...@gmail.com
redacted
pr...@gmail.com
I am not sure what the last 3 comments are above that were added today because I cannot view them (Restricted Content).
I did notice a recent change to the (new) cloud-based Map Styles editor which added the ability to edit the stroke color and width for the footprint style of buildings. That seems to be some positive progress.
I did notice a recent change to the (new) cloud-based Map Styles editor which added the ability to edit the stroke color and width for the footprint style of buildings. That seems to be some positive progress.
yb...@google.com
<codes><312220318></codes>
jo...@gmail.com
As I noted above, I noticed some minor positive progress on this bug fix. I am wondering if there are any official updates highlighting what has been fixed so far and what is currently being worked on or pending?
st...@googlemail.com
Tested again today with the latest Map Styles editor, since it has had several recent updates, but unfortunately Stroke and Width for Buildings (3d and Footprint) are still not working as expected.
am...@google.com
Adding another issue that I noticed when testing again today. Building Fill color is missing the Transparency option. If I recall correctly, in the past, 3D Buildings automatically had some transparency to allow you to see the road names within the road strokes/lines/intersections through the buildings when the map is tilted. This is especially useful when viewing metropolitan areas with lots of large/tall buildings. Screenshot attached (Transparency-Issue-Expected.jpg).
Please add this to the list of bugs/issues that I have reported above: Building Fill color is missing the Transparency option.
Please add this to the list of bugs/issues that I have reported above: Building Fill color is missing the Transparency option.
ta...@gmail.com
Back again to mention that I confirmed again today that all of these issues have persisted over into the new Cloud Based Map Styles Editor, so the bugs will all need to be addressed in the new Cloud Based Map Styles Editor and probably not in the old Map Styles Editor, which is scheduled to be retired early next year.
sk...@googlemail.com
Thank you for your message.
As per checking,
Our Engineering team is actively working on fixing the mentioned issues. We apologize for the delay and sincerely appreciate your understanding.
Rest assured that once we have receive any shareable updates, we'll let you know.
Thanks again.
cc...@android.com
Glad to hear that the related issue in
[Deleted User] <[Deleted User]>
Just got an email from Google on this issue/bug:
There has been an update in our documentation related to the stroke color and weight. The following pages have been updated. In short "Stroke color and stroke weight customizations are not available for 3D style buildings."
-https://developers.devsite.corp.google.com/maps/documentation/javascript/cloud-customization/building-style-leg#:~:text=select%203D%3A-,Note,-%3A%20Stroke%20color
-https://developers.devsite.corp.google.com/maps/documentation/javascript/cloud-customization/taxonomy
Well, I guess that is one way to fix an annoying bug... just rewrite the documentation to make it look like the bug was intentional. I have to say, that is the funniest and most annoying thing I have heard in a long time. What a joke Google Maps API has become. If the goal is to force developers to seek alternative mapping solutions, you all are succeeding.
It is also worth mentioning, I am not privileged enough to actually have access rights to view either of the documentation links that were provided (internal to Google maybe?), but I will assume that they are just trying to cover up their mistake instead of actually fixing the issues. How utterly disappointing and frustrating!
There has been an update in our documentation related to the stroke color and weight. The following pages have been updated. In short "Stroke color and stroke weight customizations are not available for 3D style buildings."
-
-
Well, I guess that is one way to fix an annoying bug... just rewrite the documentation to make it look like the bug was intentional. I have to say, that is the funniest and most annoying thing I have heard in a long time. What a joke Google Maps API has become. If the goal is to force developers to seek alternative mapping solutions, you all are succeeding.
It is also worth mentioning, I am not privileged enough to actually have access rights to view either of the documentation links that were provided (internal to Google maybe?), but I will assume that they are just trying to cover up their mistake instead of actually fixing the issues. How utterly disappointing and frustrating!
cc...@android.com
I assume they will update the doc to include fill/transparency on 3D buildings too
bf...@gmail.com
My opinion is that the bug report that is linked in
yu...@gmail.com
em...@gmail.com
We are down to less than 17 days, and still silence from Google on fixing these bugs. Morally and physically repellent, disreputable and shady behavior!
xl...@gmail.com
We really apologize for this experience.
The internal issue that we filed is still open as our engineers are still actively working on it.
Once again, apologies and thank you very much for your understanding. Once we are able to receive updates, we will surely let you know.
bf...@gmail.com
Faced the same issue with 25.1.1. Fixed it using
StaggeredGridLayoutManager.setItemPrefetchEnabled(false);
or
LinearLayoutManager.setItemPrefetchEnabled(false);
StaggeredGridLayoutManager.setItemPrefetchEnabled(false);
or
LinearLayoutManager.setItemPrefetchEnabled(false);
xl...@gmail.com
am...@google.com
The issue is fixed in latest support libraries. If you come across the issue again, please let us know by raising a new issue along with the sample code which reproduces the issue.
Thanks.
Thanks.
Description
Version used: 25.1.0
Theme used: Theme.AppCompat.Light.DarkActionBar
Devices/Android versions reproduced on: Android API 23 AVD emulator, Android 5.1 user devices
- Relevant code to trigger the issue.
The important parts of the code:
1. Uses StaggeredGridLayoutManager with multiple columns.
2. Some of the items are full span: `StaggeredGridLayoutManager.LayoutParams.setFullSpan(true)`
3. Call `RecyclerView.Adapter.notifyItemChanged()` on UI thread (e.g. post delayed Handler)
When running the example app, try flinging the RecyclerView up and down several times. It will eventually force close.
- Stack trace:
java.lang.IllegalArgumentException: Pixel distance must be non-negative
at android.support.v7.widget.GapWorker$LayoutPrefetchRegistryImpl.addPosition(GapWorker.java:110)
at android.support.v7.widget.StaggeredGridLayoutManager.collectAdjacentPrefetchPositions(StaggeredGridLayoutManager.java:2109)
at android.support.v7.widget.GapWorker$LayoutPrefetchRegistryImpl.collectPrefetchPositionsFromView(GapWorker.java:94)
at android.support.v7.widget.GapWorker.buildTaskList(GapWorker.java:213)
at android.support.v7.widget.GapWorker.prefetch(GapWorker.java:343)
at android.support.v7.widget.GapWorker.run(GapWorker.java:370)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5417)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)