DevTools failed to parse SourceMap after recent update [40119043]

Fixed

Bug

Needs-Triage-M80

Triaged-ET

RegressedIn-80

hasBisect-per-revision

Needs-Feedback

Status Update

No update yet.

Description

mj...@gmail.com

created issue #1

Feb 17, 2020 04:03PM

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36

Steps to reproduce the problem:
1. Have AdBlock (current=4.5.0) or Wappalyzer (current=5.9.0) installed; or, build a source map for your own project using Webpack (I am not sure what else is required for this case, but builds which were working are now failing)
2. Browse any web page (or, for your own project, browse your own project's compiled web page)
3. Open dev tools and view console

What is the expected behavior?
No errors in console

What went wrong?
"DevTools failed to parse SourceMap" error shown for any extensions or projects with the problem (noting that these are extensions and projects which did not show this error ~2 wks ago)

Did this work before? Yes ~2-3 weeks ago

Chrome version: 80.0.3987.106 Channel: stable
OS Version: 10.0
Flash Version:

This is affecting other users:

https://superuser.com/questions/1523427/google-chrome-devtools-failed-to-parse-sourcemap-chrome-extension/1523465
(note that the reports are all recent)

I believe this is not a regression of

https://bugs.chromium.org/p/chromium/issues/detail?id=900923 since AFAICT the failing source maps do not have a byte order mark

Comments

mj...@gmail.com <mj...@gmail.com> #2Feb 17, 2020 04:21PM

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

mj...@gmail.com <mj...@gmail.com> #3Feb 17, 2020 04:33PM

Same here.

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

pe...@chromium.org <pe...@chromium.org> #4Feb 18, 2020 03:18AM

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

sw...@chromium.org <sw...@chromium.org> #5Feb 18, 2020 12:04PM

Assigned to ya...@chromium.org.

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

mj...@gmail.com <mj...@gmail.com> #6Feb 18, 2020 01:59PM

Having the same issue:

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

mj...@gmail.com <mj...@gmail.com> #7Feb 18, 2020 02:12PM

same

ya...@google.com <ya...@google.com> #8Feb 18, 2020 03:13PM

Reassigned to sz...@chromium.org.

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

ya...@google.com <ya...@google.com> #9Feb 18, 2020 03:13PM

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

si...@chromium.org <si...@chromium.org> #10Feb 18, 2020 03:31PM

Having the same issure:

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

mj...@gmail.com <mj...@gmail.com> #11Feb 18, 2020 03:34PM

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

si...@chromium.org <si...@chromium.org> #12Feb 18, 2020 03:38PM

Same issue here.

mj...@gmail.com <mj...@gmail.com> #13Feb 18, 2020 03:44PM

Same issue here. How can i fix this bug?

mj...@gmail.com <mj...@gmail.com> #14Feb 18, 2020 03:49PM

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

si...@chromium.org <si...@chromium.org> #15Feb 19, 2020 09:25AM

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.

mj...@gmail.com <mj...@gmail.com> #16Feb 19, 2020 09:56AM

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

si...@chromium.org <si...@chromium.org> #17Feb 19, 2020 10:17AM

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!!

ys...@gmail.com <ys...@gmail.com> #18Feb 19, 2020 01:12PM

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."

mj...@gmail.com <mj...@gmail.com> #19Feb 19, 2020 03:23PM

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.

si...@chromium.org <si...@chromium.org> #20Mar 20, 2020 09:11AM

Status: Won't Fix (Obsolete)

Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...

si...@chromium.org <si...@chromium.org> #21Mar 20, 2020 09:11AM

Status: Assigned (reopened)

Any ETA on this fix? Appreciate your reply.

si...@chromium.org <si...@chromium.org> #22Apr 8, 2020 10:19AM

There's no ETA yet. I think a new version of the Google Play Services add-on in the SDK manager is going out today, but this doesn't help the issue of needing to update the emulator system images.

zb...@gmail.com <zb...@gmail.com> #23Apr 8, 2020 03:40PM

Any update on this?

Any chance you could put a note in the tutorial/setup documentation as it is infuriating (not to mention a waste of time) to follow steps exactly as described and not get something working. Resorting to Stack Overflow to find a load of hacks (and a lot of incorrect answers) for manually installing the required .apks and finally a link here to see that the issue is at least 3 weeks old with no target fix date.

si...@chromium.org <si...@chromium.org> #24Apr 9, 2020 06:54AM

I agree, please update the documentation while it is not working.

dh...@chromium.org <dh...@chromium.org> #25Apr 24, 2020 10:21AM

Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.

tv...@chromium.org <tv...@chromium.org> #26Sep 25, 2020 11:37AM

I lost hours on this problem thinking it was my fault.
Is ridiculous that a company like google do shit like that.

ya...@chromium.org <ya...@chromium.org> #27May 19, 2021 11:25AM

Reassigned to bm...@chromium.org.

This should go out today.

si...@chromium.org <si...@chromium.org> #28May 19, 2021 11:47AM

@howardb Thank Jah!

bm...@chromium.org <bm...@chromium.org> #29May 19, 2021 11:55AM

Reassigned to pf...@chromium.org.

I just updated Android in Eclipse via the SDK Manager. The first launch of my previously working application on the emulator (using Google APIs - API Level 17) generated the following error:.
GooglePlayServicesUtil(1105): Google Play services out of date. Requires 3159100 but found 3136130

Only using a new Emulator (using Google APIs - API Level 18) does the application run.

Will the older API Level 17 be updated with a new Google Play services?

va...@chromium.org <va...@chromium.org> #30Oct 7, 2021 01:05AM

Sorry, we're only committing to keeping the latest API up-to-date.

bm...@chromium.org <bm...@chromium.org> #31Oct 11, 2021 08:11AM

Reassigned to ds...@chromium.org.

How to fix this?
Google Play services out of date. Requires 3225100 but found 3136130

ds...@chromium.org <ds...@chromium.org> #32Dec 8, 2021 02:52PM

gone mad with the problem:

Google Play services out of date. Requires 3264100 but found 3225136

Plz somebody give some fix...

ds...@chromium.org <ds...@chromium.org> #33Dec 8, 2021 02:52PM

After updating my sdk to API 18, my AVD doesn't play any sound.

ds...@chromium.org <ds...@chromium.org> #34Dec 16, 2021 11:45AM

Marked as fixed.

[Empty comment from Monorail migration]

de...@chromium.org <de...@chromium.org> #35Dec 17, 2021 11:22AM

Same here...
The version of emulator (API 18, Google APIs rev 2) running Google Play services version 3.2.25 but the Play Client Library is of version 3.2.64 (rev 11).
Can we just get somewhere the older version of client library?
Or when you will update emulator with the latest Play services?

ha...@google.com <ha...@google.com> #36Jan 9, 2024 03:58AM

Found location of the old Google Play Services client library:

https://dl-ssl.google.com/android/repository/google_play_services_3225130_r10.zip

is...@google.com <is...@google.com> #37Jan 9, 2024 03:58AM

The issue is that we've paused rollout of the latest version of the Play Services APK, so many of those building with an updated client library can't update the APK on their devices. The plan is to roll back v11 of the client library until we get everything hammered out.

Version incompatibilities with the emulator are a slightly different issue (since the emulator has the APK baked in and can't update it); I'm investigating that.