chrome-web-store

问题 We registered and published a web app built with google apps script using UiApp, in the Chrome web store (CWS) a few weeks ago, without any problem. Here is the link to this item just in case http://app.thexs.ca/xsMerge Now when I go to edit this item CWS is asking for website verification through google webmaster tools for the Url associate with this web app as shown below: https://script.google.com/a/macros/thexs.ca/s/AKfycbzJ3owOK0pzCLfLTNHBQXNSWWlPFwQm2cf5EzTGwgwr24BtY43W/exec This Url

来源： https://stackoverflow.com/questions/45598029/google-group-doesnt-appear-in-chrome-developers-dashboard

来源： https://stackoverflow.com/questions/45598029/google-group-doesnt-appear-in-chrome-developers-dashboard

来源： https://stackoverflow.com/questions/45598029/google-group-doesnt-appear-in-chrome-developers-dashboard

问题 This comment mentions a partial roll out in Chrome Web Store. Where can I find that feature? My extension has more than 8,000 users but I don't see any partial roll out feature and I'm afraid to send the next version to all users at the same time. 回答1: I don't think it's documented anywhere . And I was wrong! Documentation link: Control how fast your app reaches users. In CWS lingo this is called "Controlled Rollout". If you don’t see the max deploy percentage control, it may be because of

问题 I am about to finish my Google Chrome extension. If I'm not mistaking all Chrome apps come with a capability of auto-updating. If so, is there a way for me to test it before I submit my app to the Chrome Web Store? PS. Also do I need to account for any special conditions in my extension? 回答1: To test the updating procedure, it's best to submit your extension to the Web Store in a non-public fashion. As you publish an item, you have a choice of Public, Unlisted, and Trusted Testers publication

问题 I have a Chrome packaged application that I am testing to add in-app purchases. When running the application from my own account querying getSkuDetails works fine. However, when running it from another test account, it returns TOKEN_MISSING_ERROR . I cannot find any google developer documentation to help me progress this. Has anyone come across this? 回答1: I discovered that this problem is related to the Chrome browser not being logged in. I ran into this same issue on my test machine's Chrome

问题 I have a Chrome packaged application that I am testing to add in-app purchases. When running the application from my own account querying getSkuDetails works fine. However, when running it from another test account, it returns TOKEN_MISSING_ERROR . I cannot find any google developer documentation to help me progress this. Has anyone come across this? 回答1: I discovered that this problem is related to the Chrome browser not being logged in. I ran into this same issue on my test machine's Chrome

问题 Yesterday I published my chrome extension to public with title and name as 'Bumpy'. But I couldn't able to find it in chrome web store when searched with same name. Please let me know, if someone has faced the same issue and right approach to resolve it. 回答1: It usually takes some time (more than a day or so from past experience) for the Chrome web store to index newly accepted extensions. Unless there's a specific outage, it should show up soon. If you don't see start seeing it within in a

问题 Partial success with the Chrome InApp purchase flow within a Chrome extension. I have included the buy.js file and implemented the flow as listed on the Chrome walkthrough here: https://developer.chrome.com/webstore/payments-iap Using my live extension, I have run through the flow and it works just fine. My credit card is charged and the callback returns successful, I deliver the item. When I check the google.payments.inapp.getPurchases call I can see the item listed as ACTIVE. However, when