New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Google Play Music extension (Chrome Web Store) will NOT launch

Reported by goth1...@yahoo.com, Nov 5

Issue description

Chrome Version       :Version 71.0.3578.27 (Official Build) beta (32-bit)
URLs (if applicable) :from my inspect element tool: [Deprecation] chrome.loadTimes() is deprecated, instead use standardized API: nextHopProtocol in Navigation Timing 2. https://www.chromestatus.com/features/5637885046816768.

https://chrome.google.com/webstore/detail/google-play-music/fahmaaghhglfmonjliepjlchgpgfmobi/related

(anonymous) @ m=consumer:1506

Other browsers tested: n/a

What steps will reproduce the problem?
(1)clicking on launch button does nothing


What is the expected result?
for the app to launch

see all the complaints from end users in the reviews. do you even read them?

What happens instead? nothing


Please provide any additional information below. Attach a screenshot if possible.
this app is not letting me upload to my google play music library because it's not working at all.



 
Screenshot 2018-11-05 at 18.01.29 - Display 1.png
105 KB View Download
further info:
hisense C11 ARM chromebook about 2 years old. 
Labels: Needs-Triage-M71
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET OS-Chrome
Thanks for filing the issue!

From comment#1, this seems to be related to Chromebook hence adding appropriate OS label and requesting someone from respective team to have look into this for further inputs.
Components: -Blink>PerformanceAPIs
also getting a "could not identify computer" notice when i direct upload from my chromebook. the operation also refuses to let me screen grab to show you.
Labels: -Pri-3 Hotlist-ConOps-CrOS Hotlist-ConOps-Source-Forum Pri-2
Summary: Google Play Music extension (Chrome Web Store) will NOT launch (was: music manager will NOT launch)
From the link <https://chrome.google.com/webstore/detail/google-play-music/fahmaaghhglfmonjliepjlchgpgfmobi/related>, this looks to be 

Google Play Music on the Chrome web store
Version: 1.396.0
Updated: September 26, 2018
Seeing these issues from the reviews on the Chrome web store:
(1) Users unable to launch or open the application on M70 or M71
(2) Users keep getting a message "Could not identify your computer" when they try to upload music
(3) Users having issues when the account used for Chrome sign-in is different than account used for Google Music (possibly due to legacy GSuite accounts)

Components: Webstore
Blocking: 877240
Cc: dominickn@chromium.org gab@chromium.org
Components: -Webstore Platform>Extensions Platform>Apps
Labels: -Type-Bug -Pri-2 -OS-Chrome OS-All Pri-1 Type-Bug-Regression
Owner: rdevlin....@chromium.org
Status: Assigned (was: Unconfirmed)
The internal bug is b/119936479.

This is really bad. P1 at least, possibly P0.

I bisected this down to https://chromium.googlesource.com/chromium/src/+/5caf3124fbb3024a441d97d206c5caac5a305302.

mark@finger zsh% python bisect_builds.py -o -g 70.0.3538.0 -b 71.3578.0.0 -a mac -p /tmp/udd
[…]
You are probably looking for a change made after 595148 (known good), but no later than 595149 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/42f4734035b913b1689a72f2cbe698d66fb387b0..5caf3124fbb3024a441d97d206c5caac5a305302
Cc: atordillos@google.com

Comment 13 Deleted

Logged messages:

[15007:775:1206/152443.367940:ERROR:extension_function_dispatcher.cc(586)] Unknown Extension API - musicManagerPrivate.getDeviceId
Cc: rdevlin....@chromium.org
Owner: mark@chromium.org
I don't think that's the right bisect.

I reverted that locally on ToT (Linux), and the same issue exists.  I also tried on Chrome 70.0.3538.110 (both Linux and Windows), and the issue reproduces there as well (note that that CL landed in 71.0.3565.0).  Note that in all of these cases, I also saw an error thrown in the app's background page about the user not being signed in.  I'm not sure if that's relevant to the failures or not, and all the code is minified, so difficult to say.  But in looking at the API calls that are triggered, I don't see any that would cause an app window to open (i.e., no calls to chrome.app.window API).

I think we're looking for a different cause.

Are we sure that something changed in Chromium, and not in the platform app?
Although that error message does look suspicious, and I'm not seeing that on my local builds.  Hmm...
Cc: -rdevlin....@chromium.org mark@chromium.org
Owner: rdevlin....@chromium.org
Might have been over-eager.  Let me investigate more.  (Though I'm still curious why this is doesn't work in M70 - before that cl - on either Linux or Win.  Is that expected?)
I tested this on Chrome 70 earlier today and it was working. After upgrading to 71, it fails with the error message: "Unchecked runtime.lastError while running musicManagerPrivate.getDeviceId: Access to extension API denied."

Labels: ReleaseBlock-Stable M-71
@18 Which OS?  I'm still seeing music fail to open on Linux/Win, even on 70.

@11, @14, @15, @16, @17: I've been able to reproduce the log statement through an erroneously-passing browser test (MusicManagerPrivateTest.DeviceIdValueReturned).  I've fixed the production change in https://chromium-review.googlesource.com/c/chromium/src/+/1367114, but not updated the test.  I'd like to make sure this fixes the play music app as well, but have yet to be able to launch it on a particular OS.  Is it still supported outside of CrOS?

While we discuss, reapplying RBS for 71.
I can confirm that https://crrev.com/c/1367114 fixes the Google Play Music app (fahmaaghhglfmonjliepjlchgpgfmobi) on macOS. Tested on the trunk at b41d1d9efaca.

Regarding chrome/test/data/extensions/platform_apps/music_manager_private/device_id_value_returned/chrometest.js, I get it, but wow. Just wow.
Great - I'll send out https://chromium-review.googlesource.com/c/chromium/src/+/1367114 for review, since I think that'll be cleaner than a merged-revert (which has significant conflicts).

For the record, can you let me know the steps you used to launch the app (from trunk)?  I'm still unable to, which makes me a bit uneasy.
Sure!

0a. https://chrome.google.com/webstore/detail/google-play-music/icppfcnhkcmnfdhfhphakoifcfokfdhg, “Add to Chrome”.
0b. Chrome must be signed in.
1. chrome://apps, click “Play Music”.
2. https://play.google.com/music/listen, drag an mp3 onto the web site.

When the app is working (expected behavior): step 1 will pop open a small window. Clicking “SIGN IN” in that window will open the page from step 2. Upon completing step 2, the mp3 will be added to the library.

When the app is not working (observed behavior): step 1 does nothing except close the chrome://apps tab. Upon attempting step 2, the message “Could not identify your computer” appears at the bottom left of the page.
Cc: pbomm...@chromium.org kbleicher@chromium.org
Labels: OS-Chrome
Is this M71 regression applicable to Windows, Mac and Linux?
Per comments #1, #9, #11 and  internal mail thread "Re: Chrome Extension for Google Play Music broken in M71", this is reported on Chrome OS.


@23: From comment #22 (and the labels on the bug), it sounds like this affects all desktop platforms (Win, Mac, Linux, CrOS).  If that's the case, I think it should be RBS.  One potential factor is how many users install Google Play Music outside of CrOS (which I don't know off the top of my head, and I'm not sure we can disclose on a public bug); that may influence whether we merge it to M71 on non-CrOS.
Project Member

Comment 26 by bugdroid1@chromium.org, Dec 7

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b0836cf405ec25c63308dbddb72c046f651286e1

commit b0836cf405ec25c63308dbddb72c046f651286e1
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Fri Dec 07 04:42:09 2018

[Platform Apps] Include uncompiled app sources in API registration]

Include un-compiled API sources in the list of APIs to register for
Chrome API functions.

Bug:  902116 

Change-Id: Ie10134207e4a0d8c4ecb1eb6a0b8d3b2e9d4b61d
Reviewed-on: https://chromium-review.googlesource.com/c/1367114
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#614602}
[modify] https://crrev.com/b0836cf405ec25c63308dbddb72c046f651286e1/chrome/browser/apps/platform_apps/api/BUILD.gn

Labels: Merge-Request-72
NextAction: 2018-12-10
Status: Fixed (was: Assigned)
This should be fixed with #26.

We'll at least want to merge this to 72, and possibly 71.  Requesting merge to 72, though I'll wait 'til Monday to allow it time to bake on Canary.

If this is blocking Chrome OS M71 stable we'll need the M71 merge *today* since we're targeting stable soon.  Thanks
Labels: Hotlist-ConOps
I’d be generally inclined to push for this on 71 for all platforms.

Someone from Chrome OS needs to make the call about whether an immediate merge to 71 is necessary, or if 71 can be held for this to bake, or if it’s OK to wait for a 71 follow-up release. I understand that Google Play Music is probably a bit more significant to Chrome OS than other desktop platforms.
Labels: Merge-Request-71
Per #28, also requesting M71 merge now.
Project Member

Comment 32 by sheriffbot@chromium.org, Dec 7

Labels: -Merge-Request-71 Hotlist-Merge-Review Merge-Review-71
This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Merge-Request-72 -Merge-Review-71 Merge-Approved-71 Merge-Approved-72
Approving merge to M71 branch 3578 and M72 branch 3626 as it is needed for Chrome OS urgently per offline group chat, risk is low. 

rdevlin.cronin@ is continue going to monitor canary data and update on Monday. Thank you.
Project Member

Comment 34 by bugdroid1@chromium.org, Dec 7

Labels: -merge-approved-72 merge-merged-3626
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b24227d1296655e9b0dd3c166d597fe834f45f5e

commit b24227d1296655e9b0dd3c166d597fe834f45f5e
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Fri Dec 07 23:45:30 2018

[M72][Platform Apps] Include uncompiled app sources in API registration]

Include un-compiled API sources in the list of APIs to register for
Chrome API functions.

Bug:  902116 

TBR=rdevlin.cronin@chromium.org

(cherry picked from commit b0836cf405ec25c63308dbddb72c046f651286e1)

Change-Id: Ie10134207e4a0d8c4ecb1eb6a0b8d3b2e9d4b61d
Reviewed-on: https://chromium-review.googlesource.com/c/1367114
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#614602}
Reviewed-on: https://chromium-review.googlesource.com/c/1368786
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/3626@{#157}
Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437}
[modify] https://crrev.com/b24227d1296655e9b0dd3c166d597fe834f45f5e/chrome/browser/apps/platform_apps/api/BUILD.gn

Labels: -Merge-Approved-71 Merge-Merged-71-3578
The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/115641c5080ee363fb7a173b7e1142b303333c5c

Commit: 115641c5080ee363fb7a173b7e1142b303333c5c
Author: rdevlin.cronin@chromium.org
Commiter: rdevlin.cronin@chromium.org
Date: 2018-12-08 00:09:48 +0000 UTC

[M71][Platform Apps] Include uncompiled app sources in API registration]

Include un-compiled API sources in the list of APIs to register for
Chrome API functions.

Bug:  902116 

TBR=rdevlin.cronin@chromium.org

(cherry picked from commit b0836cf405ec25c63308dbddb72c046f651286e1)

Change-Id: Ie10134207e4a0d8c4ecb1eb6a0b8d3b2e9d4b61d
Reviewed-on: https://chromium-review.googlesource.com/c/1367114
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#614602}
Reviewed-on: https://chromium-review.googlesource.com/c/1369028
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#882}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
Project Member

Comment 36 by bugdroid1@chromium.org, Dec 8

Labels: merge-merged-3578
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/115641c5080ee363fb7a173b7e1142b303333c5c

commit 115641c5080ee363fb7a173b7e1142b303333c5c
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Sat Dec 08 00:09:48 2018

[M71][Platform Apps] Include uncompiled app sources in API registration]

Include un-compiled API sources in the list of APIs to register for
Chrome API functions.

Bug:  902116 

TBR=rdevlin.cronin@chromium.org

(cherry picked from commit b0836cf405ec25c63308dbddb72c046f651286e1)

Change-Id: Ie10134207e4a0d8c4ecb1eb6a0b8d3b2e9d4b61d
Reviewed-on: https://chromium-review.googlesource.com/c/1367114
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#614602}
Reviewed-on: https://chromium-review.googlesource.com/c/1369028
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#882}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
[modify] https://crrev.com/115641c5080ee363fb7a173b7e1142b303333c5c/chrome/browser/apps/platform_apps/api/BUILD.gn

Labels: Needs-Feedback
Tried checking the issue on reported chrome version 71.0.3578.27 using Mac 10.14.1 and on the latest canary 73.0.3636.0 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://chrome.google.com/webstore/detail/google-play-music/fahmaaghhglfmonjliepjlchgpgfmobi/related
3. Clicked Add to chrome
Then tried launching the app, we couldn't launch it on reported version and on the latest version too. 

@Devlin Cronin: Could you please let us know if any fixes are yet to land. That would be helpful if mentioned, if we have missed anything in the process. 

Thanks!
The NextAction date has arrived: 2018-12-10
Labels: -Needs-Feedback
@37: Please use the steps mark@ provided in #22 (copied here):

0a. https://chrome.google.com/webstore/detail/google-play-music/icppfcnhkcmnfdhfhphakoifcfokfdhg, “Add to Chrome”.
0b. Chrome must be signed in.
1. chrome://apps, click “Play Music”.
2. https://play.google.com/music/listen, drag an mp3 onto the web site.

When the app is working (expected behavior): step 1 will pop open a small window. Clicking “SIGN IN” in that window will open the page from step 2. Upon completing step 2, the mp3 will be added to the library.

When the app is not working (observed behavior): step 1 does nothing except close the chrome://apps tab. Upon attempting step 2, the message “Could not identify your computer” appears at the bottom left of the page.
I did just verify that this is working as expected in 73.0.3636.0 (Official Build) canary (64-bit) on macOS 10.14.2 18C54.
Anyone test it on Chrome OS? Mini Player and uploading gets stuck on this indefinitely: "Setting up Google Play Music for Chrome..."

Version 73.0.3636.0 (Official Build) canary (64-bit)
 
1381.0.0 (Official Build) canary-channel eve
 
Screenshot 2018-12-10 at 1.24.39 PM.png
1.1 MB View Download
Labels: Needs-Feedback
When tried checking the issue on reported chrome version 71.0.3578.27 using Mac 10.14.1 and on the latest canary 73.0.3636.0 with the exact steps mentioned in C#37/C#22.

Observed similar behaviour mentioned in C#41 i.e., the app got stuck at "Setting up Google Play Music for Chrome..." Attaching the screenshot of the same for reference.

@Devlin Cronin: Please let us know if anything is being missed here.

Thanks!
902116 CL Verif.png
634 KB View Download
Labels: -Needs-Feedback TE-Verified-72.0.3626.14 TE-Verified-M72
++ This seems to be fixed on chrome version 72.0.3626.14 using Mac 10.14.1
Attaching the screenshot of the same for reference.
Observed that we were able to add mp3 files successfully to Google Play Music.
Hence adding verified labels.

Thanks!
Screenshot 2018-12-11 at 18.24.05.png
659 KB View Download
Thanks, vamshi.kommuri@!  Re #42, version 71.0.3578.27 is not expected to work, since the M71 merge only went into 71.0.3578.89.  So I think we're all good here.
Labels: Needs-Feedback
Status: Assigned (was: Fixed)
Tried verifying the fix on chrome version# 71.0.3578.95 using Mac 10.13.6, facing the issue on playing the mp3 file(seeing as Setting up Google Play Music for Chrome...). Please find the attached screencast for reference.

Note: Making this issue to Assigned status and requesting Dev to provide confirmation on this issue.

Thanks!
902116.webm
5.9 MB View Download
Viswa, the Play Music in your chorome://apps behaves as icppfcnhkcmnfdhfhphakoifcfokfdhg and not fahmaaghhglfmonjliepjlchgpgfmobi. I originally gave the wrong app ID in comment 22, and corrected myself in comment 24.

Please check which one you’ve installed in chrome://extensions. If it’s icppfcnhkcmnfdhfhphakoifcfokfdhg, remove that, and install the correct one from https://chrome.google.com/webstore/detail/google-play-music/fahmaaghhglfmonjliepjlchgpgfmobi instead.
Status: Fixed (was: Assigned)
We believe that this is working as expected per offline discussion. Notably, the portion that regressed in Chrome 71 is fixed and is back to working as it did in Chrome 70.

There may be other misbehaviors here for which separate bugs should be filed.

Thanks, everyone, for your help.
There is one another way where we can still reproduce the issue, but that's been the behavior even on previous version of Chrome stable as well. 

1. Install Google Play Music App "https://chrome.google.com/webstore/detail/google-play-music/fahmaaghhglfmonjliepjlchgpgfmobi"
2. Try to launch Google play music app from Webstore tab or Chrome://apps tab
3. Nothing happens
4. Try to sign-in to Chrome 
5. repeat the step 2, Google play music doesn't launch.

If anyone lands into this state, The only way this works as expected is when we uninstall the App which we have installed in step one and try to re-install back again after signin to chrome this works. 
[Deprecation] HTML Imports is deprecated and will be removed in M73, around March 2019. Please use ES modules instead. See https://www.chromestatus.com/features/5144752345317376 for more details.
listen.js:135 [Deprecation] document.registerElement is deprecated and will be removed in M73, around March 2019. Please use window.customElements.define instead. See https://www.chromestatus.com/features/4642138092470272 for more details.
(anonymous) @ listen.js:135
2listen.js:3951 paper-toolbar is deprecated. Please use app-layout instead!
ready @ listen.js:3951
dn.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
listen.js:3951 paper-toolbar is deprecated. Please use app-layout instead!
ready @ listen.js:3951
clients5.google.com/:6 Uncaught ReferenceError: gbar is not defined
    at onload (clients5.google.com/:6)
imasdk.googleapis.com/js/sdkloader/ima3.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
ad.doubleclick.net/activity;src=2542116;type=googplay;cat=play-012;ord=4213997193697;gtm=2wgbc0;auiddc=318979638.1545149033?:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
listen.js:373 Could not find style data in module named iron-flex
cssFromModule @ listen.js:373
ad.doubleclick.net/activity;src=2542116;type=googplay;cat=play-013;ord=1;num=7518392943821;gtm=2wgbc0;auiddc=318979638.1545149033?:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
chrome-extension://cfnpidifppmenkapgihekkeednfoenal/content/content.js:1 Feedback rendered
/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
5Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/antiphishing.js:1 Sending APH request...
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Sent message with requests
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Got repsonses
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Array(0)
undefined:1 Failed to load resource: the server responded with a status of 404 ()
2/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/antiphishing.js:1 Sending APH request...
listen#/home:1 Unchecked runtime.lastError: The message port closed before a response was received.
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Sent message with requests
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Got repsonses
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Array(0)
chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13 Uncaught (in promise) ReferenceError: currentURL is not defined
    at then.catch.e (chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13)
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/antiphishing.js:1 Sending APH request...
ad.doubleclick.net/activity;src=2542116;type=googplay;cat=play-011;ord=1;num=1768091969797;gtm=2wgbc0;auiddc=318979638.1545149033?:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Sent message with requests
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Got repsonses
/home/chronos/u-9355671486b82d91a30ba2c33262de9393384ab6/Extensions/cfnpidifppmenkapgihekkeednfoenal/3.0.1_0/content/searchAnalyzer.js:1 Array(0)
chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13 Uncaught (in promise) ReferenceError: currentURL is not defined
    at then.catch.e (chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13)
3services/log?u=0&format=jsarray&xt=CjUKATASMEFNLVdiWGlFal9lYVQ1ZVJWTHpJQnpPLVBzNkRVZ3FPWVE6MTU0NTE0OTA1MDM1Ng%3D%3D&dv=223989270&obfid=15277113509605047594:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13 Uncaught (in promise) ReferenceError: currentURL is not defined
    at then.catch.e (chrome-extension://mlomiejdfkolichcflejclcbmpeaniij/dist/content_script_bundle.js:13)
/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
services/log?u=0&format=jsarray&xt=CjUKATASMEFNLVdiWGlFal9lYVQ1ZVJWTHpJQnpPLVBzNkRVZ3FPWVE6MTU0NTE0OTA1MDM1Ng%3D%3D&dv=223989270&obfid=15277113509605047594:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
6/play/log?format=json&authuser=0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
listen.js:1203 POST https://play.google.com/play/log?format=json&authuser=0 net::ERR_BLOCKED_BY_CLIENT
qx.send @ listen.js:1203
(anonymous) @ listen.js:1634
ej @ listen.js:765
d.mW @ listen.js:1633
d.z$ @ listen.js:1633
d.flush @ listen.js:1633
c @ listen.js:1191

c'mon let's fix this mess!
here is the rest of the story from my inspection tool on a chromebook. it behooves someone to burn some midnight oil to fix this mess:

Active resource loading counts reached a per-frame limit while the tab was in background. Network requests will be delayed until a previous loading finishes, or the tab is brought to the foreground. See https://www.chromestatus.com/feature/5527160148197376 for more details
m=consumer:1496 [Deprecation] chrome.loadTimes() is deprecated, instead use standardized API: nextHopProtocol in Navigation Timing 2. https://www.chromestatus.com/features/5637885046816768.
(anonymous) @ m=consumer:1496
/webstore/ajax/logreferrerchain/fahmaaghhglfmonjliepjlchgpgfmobi?hl=en-US&gl=US&pv=20181009&mce=atf%2Cpii%2Crtr%2Crlb%2Cgtc%2Chcn%2Csvp%2Cwtd%2Cnrp%2Chap%2Cnma%2Cnsp%2Cdpb%2Cc3d%2Cncr%2Cctm%2Cac%2Chot%2Cmac%2Cfcf%2Crma%2Clrc&_reqid=342538&rt=j:1 Failed to load resource: the server responded with a status of 400 ()
null:1 Failed to load resource: the server responded with a status of 404 ()
btw, where is the app in the web store? i can't find it anywhere to d/l it?

Comment 54 Deleted

Deleted the previous comment since the bug is about launching the mini player.
WAI on Google Chrome 71.0.3578.94 (Official Build) beta (64-bit)

Might be handy if the apps have different icons. In screenshot:

Web app and Mini player look the same. Third one (white round background) is the Android Play music app.
Screenshot 2018-12-19 at 11.19.09 AM.png
106 KB View Download
Labels: Merge-Merged-72-3626
The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/b24227d1296655e9b0dd3c166d597fe834f45f5e

Commit: b24227d1296655e9b0dd3c166d597fe834f45f5e
Author: rdevlin.cronin@chromium.org
Commiter: rdevlin.cronin@chromium.org
Date: 2018-12-07 23:45:30 +0000 UTC

[M72][Platform Apps] Include uncompiled app sources in API registration]

Include un-compiled API sources in the list of APIs to register for
Chrome API functions.

Bug:  902116 

TBR=rdevlin.cronin@chromium.org

(cherry picked from commit b0836cf405ec25c63308dbddb72c046f651286e1)

Change-Id: Ie10134207e4a0d8c4ecb1eb6a0b8d3b2e9d4b61d
Reviewed-on: https://chromium-review.googlesource.com/c/1367114
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#614602}
Reviewed-on: https://chromium-review.googlesource.com/c/1368786
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/3626@{#157}
Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437}
is any of this going to be fixed of should we all abandon google altogether? the lack of customer support and indifference is not going bode well for all google/chrome products in the future. i had good vibes when i first started using  google but now i see nothing but trouble for google. this not good P.R. need to step up your game.
@reporter: If you are facing issues that are different from the misbehavior/steps mentioned in C#39 then please file a new issue.

As confirmed in C#48,C#49 this issue addressed M-71 specific regression and there may well be other issues as well and would be good to have them addressed separately. 

Apologies for inconvenience and please let us know when you have filed the other issue with specific repro steps. 

Sign in to add a comment