Issue metadata
Sign in to add a comment
|
Inline install was working... now fails.
Reported by
rboissi...@tripadvisor.com,
Jan 11 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Go to https://www.tripadvisor.com/ShowForum-g34515-i19-Orlando_Florida.html 2. Click "Add to Google Chrome" in the banner ALSO: In the Developer console I tried... chrome.webstore.install('https://chrome.google.com/webstore/detail/oiekdmlabennjdpgimlcpmphdjphlcha',function(x){alert('Good:'+x)},function(x){alert('FAIL:'+x)}); I get "Could not fetch data from the Chrome Web Store" What is the expected behavior? Should get a permissions dialogue to complete the install. What went wrong? The call to chrome.webstore.install always fails... Per other threads... I've tried to access https://chrome.google.com/webstore/inlineinstall/detail/oiekdmlabennjdpgimlcpmphdjphlcha And I get a 500 error WebStore page: https://chrome.google.com/webstore/detail/tripadvisor-browser-butto/oiekdmlabennjdpgimlcpmphdjphlcha Did this work before? Yes Was a name change... Jan 4th, 2016 Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.12.2 Flash Version: Shockwave Flash 24.0 r0
,
Jan 11 2017
Thank you for looking into this. Any idea when we should expect a fix? If it's going to last a while we will perhaps disable inline install. I have recently applied to have multi-domain inline install enabled and so I was wondering if this recent breakage was in any way related. Could you please provide a snippet of detail of the bug? Is there something that I could do to the extension to mitigate this for now? Is there a site where I can see the detail/status of the bug, or is that strictly an internal tool?
,
Jan 12 2017
We are experiencing the same problem, and also have applied for the multi-domain inline install functionality as described here: https://bugs.chromium.org/p/chromium/issues/detail?id=152427
,
Jan 13 2017
Yes the bug is related to the multi-domain inline install feature. Since the coming Monday is a public holiday, the fix is expected to go out on late Tuesday afternoon.
,
Jan 18 2017
I can confirm that for us the issue has been resolved. Thanks for the effort.
,
Jan 18 2017
The single domain install is working... Still no multiple domains however... I'm getting this error: "Installs can only be initiated by one of the Chrome Web Store item's verified sites." When I try on any of the other sites which I submitted to have enabled for multi domain inline install... Is there something else that I need to do?
,
Jan 18 2017
Close the bug as fixed. To rboissinot, from the returned json (chrome.google.com/webstore/inlineinstall/detail/oiekdmlabennjdpgimlcpmphdjphlcha ) it looks like you have only one verified site. "verified_site":"https://tripadvisor.com".
,
Jan 18 2017
Agreed... question is how do I add more? The chrome store UI does not let me select more than one.
,
Jan 19 2017
To rboissinot, you need verify your group publisher(***@googlegroups.com)'s ownership with all your domains through Google's Webmaster tools. https://www.google.com/webmasters/tools Here is a Youtube video you can refer to. https://www.youtube.com/watch?v=wBAccFPnoeg Please notice, since you cannot login as a group, the first step you need to do is to verify the ownership of a single user, and then the user can add the group as a owner of the domain.
,
Jan 19 2017
OK well that is certainly not obvious... and doesn't work anyway... My personal account has all of domains I need already verified. When I try to add the group publishing account, I get an error dialog: -------------- Can't Add User (*removed*)@googlegroups.com is not associated with a Google Account. -------------- Now what?
,
Jan 19 2017
Here is what I have done, In any domain you want to verify, click tools button and select "Users and Property Owners", Instead of clicking "ADD A NEW USER" button, click "Manage property owners" which is left to it. At bottom left corner, there is a "Add an owner" button, click it and enter your group account, then continue. You group account will be added as an owner. Sorry you might found I tested your group account with a test domain.
,
Jan 19 2017
That does not work either... I get a similar message. We could not find a Google Account for (*removed*)@googlegroups.com I have attached a screenshot
,
Jan 19 2017
OK I found what was causing this to fail. The name of the Group Publishing account has changed (and consequently the email address). The email address listed in the WEB Store was the OLD group email address, it did not update to reflect the new address. I went back to the group management and set the email address back to the original value, and that I was then able to add as a verified user. Going to https://chrome.google.com/webstore/inlineinstall/detail/(extension id) the new verified domains are not appearing yet... but I will check after a while to see if that updates. Perhaps some cache or publication delay...??? So I'll give that a bit of time to see if it's now fixed.
,
Jan 20 2017
OK one day later, the list of Verified Domains has not changed for our extension. I tried adding a couple more to the group account, and the account is listed as an owner for the domain when I look at the WMC. Please help...
,
Jan 23 2017
+yczhao, can you comment on #15?
,
Jan 23 2017
,
Jan 23 2017
I can see the only verified domain added for your group publisher is https://tripadvisor.com Add I tried your group publisher(taseo4NNNNNN-NNNNNNNNNN) with our test domain again, and there is no problem. The new results appear immediately. Can you double check how you add owners?
,
Jan 23 2017
OK - Have reread this thread... I guess the nuance that I missed was that the group had to be added as an "owner"... not just full access. That seems to be working! Thanks again and sorry for the confusion.
,
Apr 20 2018
What is a "group"? Are you just referencing the account that publishes the extensions, or is it something else? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lottie@chromium.org
, Jan 11 2017Status: Assigned (was: Unconfirmed)