Fixed
Status Update
Comments
en...@google.com <en...@google.com> #2
Information redacted by Android Beta Feedback.
en...@google.com <en...@google.com> #3
Why hasn't this more stars? I have this in Beta right now and it's so annoying!
en...@google.com <en...@google.com> #4
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
en...@google.com <en...@google.com> #5
The issue is not reproducible on our internal development build (which is ahead of the public release). Please test it on the final public release and let us know if you are still having issues.
en...@google.com <en...@google.com> #7
I cannot reproduce anymore on S2B2.211203.006
pa...@tokiomarine.com.br <pa...@tokiomarine.com.br> #9
Many requests for addresses in Brazil are still experiencing problems. Any deadline for general normalization?
jh...@google.com <jh...@google.com> #10
If you are still experiencing issues, please open new issues and/or support cases. We don't expect for the symptoms mentioned to still be occurring due to this particular issue.
Description
Summary: administrative_area_level_1 short_name fields filled with long-name values.
Description: We are experiencing an issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific.
The symptoms are
short_name
fields filled withlong_name
values, in particular for US states.Our engineering team continues to investigate the issue.
We will provide an update by Friday, 2024-06-28 21:25 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis:
administrative_area_level_1
short_name
fields are containinglong_name
responsesWorkaround: None at this time.