Component Filtering does not always return existing 4-digit and 5-digit ZIP codes [73030863]

Fixed

Bug

adexe s nau

Status Update

No update yet.

Description

ar...@gmail.com

created issue #1

Feb 7, 2018 09:57AM

Hello,

We are facing issue to get location details from postal code.

We tried below api to get location details from Postal code
"

http://maps.googleapis.com/maps/api/geocode/json?components=postal_code:l24&sensor=false"
but it returns zero result.

So we are using places api to get location details
"

https://maps.googleapis.com/maps/api/place/textsearch/json?query=postal_code:l24&key="
It returned result but it has valid details.
But same api is not returns valid details for postal code l21.

Would you please let us know How we can get valid details for each postal code?

Please let us know if we are missing anything.

Thanks

Comments

vt...@google.com <vt...@google.com> #2Feb 7, 2018 03:05PM

Status: Won't Fix (Intended Behavior)

I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130

ar...@gmail.com <ar...@gmail.com> #3Feb 8, 2018 10:07AM

Same here.

"Google Play services out of date. Requires 3159100 but found 3136130"

device-2018-02-08-150810.png

57 KB

View

Download

vt...@google.com <vt...@google.com> #4Feb 9, 2018 09:08AM

Status: Assigned (reopened)

me as well....
Google Play services out of date. Requires 3159100 but found 3136130

an...@google.com <an...@google.com> Feb 9, 2018 09:59AM

Reassigned to mi...@google.com.

mi...@google.com <mi...@google.com> #5Feb 9, 2018 10:23AM

I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130

fr...@gmail.com <fr...@gmail.com> #6Jun 26, 2018 12:15AM

Having the same issue:

07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130

mi...@google.com <mi...@google.com> #7Jun 29, 2018 07:39AM

same

mi...@google.com <mi...@google.com> #8Jul 12, 2018 10:31AM

SAME ! - Google can't do sth working in 100 percent?

mi...@google.com <mi...@google.com> #9Aug 9, 2018 05:14PM

same issue - Google Play services out of date. Requires 3159100 but found 3158130

ti...@regrapes.de <ti...@regrapes.de> #10Nov 21, 2018 10:26AM

Having the same issure:

07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130

mi...@google.com <mi...@google.com> #11Nov 21, 2018 02:44PM

API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130

co...@gmail.com <co...@gmail.com> #12Jan 17, 2019 05:34PM

Same issue here.

mi...@google.com <mi...@google.com> Jun 8, 2020 07:16PM

Reassigned to gm...@google.com.

ma...@gmail.com <ma...@gmail.com> #13Oct 4, 2022 09:18PM

Comment has been deleted.

Message last modified on Nov 15, 2022 05:14PM

ta...@gmail.com <ta...@gmail.com> #14Dec 31, 2022 10:54PM

We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".

pa...@gmail.com <pa...@gmail.com> #15Jan 21, 2023 08:05PM

Thanks for the update @sbarta. It is good that you are keeping us informed. This is a very critical and blocking bug for anyone developing with maps.

mi...@google.com <mi...@google.com> #16Aug 25, 2023 09:28AM

FYI also getting same with PlusClient sign in, so this is not just a maps issue:

ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED

07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013

mi...@google.com <mi...@google.com> #17Dec 5, 2024 09:47AM

Marked as fixed.

Same page here!

07-31 22:47:40.277: W/GooglePlayServicesUtil(1009): Google Play services out of date. Requires 3159100 but found 3158130

Thing is: we work under timelines too, and we need this fix quick! I cannot go wondering around asking for cellphones all over the place... I used to have this fixed with my emulators!!

ri...@ingka.com <ri...@ingka.com> #18Dec 10, 2024 05:55PM

Issue 36949180

requires a change to the emulator images. A comment just added states: "This will be fixed with the next update to the emulator system image, due out within a few weeks."

mi...@google.com <mi...@google.com> #19Dec 12, 2024 12:16PM

The Play Services team knows about this issue and is working on it with a high priority. The fix for this will go in the same emulator image in the same timeframe. Sorry I'm being vague about when it'll go out; I don't want to tell you something and then have us miss it. I'll update this bug when I know more.