Status Update
Comments
ee...@google.com <ee...@google.com> #2
Thanks for the post!
We are currently looking into it and we'll get back to you as soon as we have more information to share or if we need more details from you.
ee...@google.com <ee...@google.com> #3
Also, we will be removing your name in your comment for your security as this is considered as Personal Identifiable Information (PII).
hj...@gmail.com <hj...@gmail.com> #4
Thank You. I notice, some places in Ukraine (villages) is working good. But Kyiv addresses have the bug. May be this info helps to You.
ee...@google.com <ee...@google.com> #5
Thank you for waiting!
Upon checking, it appears that this is a duplicate of
hj...@gmail.com <hj...@gmail.com> #6
Yes. It is a duplicate. Thank You for link. I unhappily surprised this bug age is 7+ years(!!!) and is not fixed yet. Why???
Description
#IMPORTANT: If your production system or service is down file a Severity 1 support case at console.cloud.google.com/google/maps-apis
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but not API keys or client ID credentials.
To learn more about personal data, visithttps://en.wikipedia.org/wiki/Personal_data
===========================================================================================
Issue report
What steps will reproduce the problem? Please provide a link to a demonstration page if at all possible, or attach code.
When I do query with parameter "language=ru" I get Ukrainian names and address components instead of Russian names and address components (see Screens in attachments).
Query string for example (replace "<SessionToken>" and "<APIKey>" for Your values):
Russian is the native language in Ukraine for more than 50% citizens. And all places have Russian names along with Ukrainian names. Furthermore "Place Autocomplete" queries return Russian descriptions of predictions. Consequently Russian names exist in Your database, but Places API loose them :(
Best Regards, <REDACTED>