I have a chrome extension with a lot of users, and I want to update it. I have everything ready but I need to test the update in order to make sure that the current users won't lose the data. Is there any way to publish the new version only to the trusted testers?
I created a tester group.
I insert trusted testers e-mail accounts.
I am signed to Google Chrome browser under the testing account
I am signed to Google Chrome webstore under the testing account
But I still can't see the new version. The button "Publish to tester accounts" is only on the unpublished extension.
The only way I was able to publish a new version to testers is by doing exactly that, creating a new version specifically for testing.
The way that the dashboard is currently set up you would have to un-publish your current application before you can publish it to the test accounts, and that is something I doubt you want to do.
So in your case, I'd do the following
Set up a 'testing' version of your application with your current code.
Publish it to your test group and have them use it for a while until
they have the data you are concerned about.
Update the 'testing' version with your changes and see if the data
is missing.
Google has recently solved this with a new update.
So right now there is a option to publish the new version just to the testers.
The extension will be hidden for a while, but when you publish it again to public, it is all done.
Related
When I deployed a new version of a script using the legacy editor, the "web app meta-version" was set to that version number and the link that my users have will execute the new version.
When I use the new editor the "web app meta-version" is not updated but a new "default meta-version" is created instead and a new ID/url is generated for it with the new version number shown there. The "web app meta-version" is left with the older numbered version of the code.
I do not want to update the links that the users have. Is there no way with the new editor to update the "web app meta-version" version number? An alternative would be to be able to set the required ID/url for the "default meta-version".
This is a known issue
And it seems that Google have recognized it.
Go give this issue a ☆:
https://issuetracker.google.com/175944464
Please don't commment with "+1", if you just click the star you will be subscribed and functions as a "+1"
I can now see (and have "starred") the issue number shown in iansedano's answer. However, that is a duplicate issue and the original issue to which it refers (https://issuetracker.google.com/issues/175811864) is inaccessible. I cannot imagine that having "starred" duplicates makes much difference to anyone responsible for resolving the original.
I am making a chrome extension, and for the purposes of my Chrome Extension, I am wanting users to be able to sign in to their Google account so they can send information to a server. I have been reading about user authentication and whatnot from the Google documents, but this is for apps that are being published into the store, and mine is in development. This is brand new territory for me, and I am lost. I feel like there's something that I must be missing, but I don't know how to get started.
Thanks.
Check this documentation about the quick way of loading up your working directory for testing. Extensions that you download from the Chrome Web Store are packaged up as .crx files, which is great for distribution, but not so great for development.
I'm very, very new to Windows Dev Center, and I'm hoping someone will be able to clear some things up for me. There is an app already within the Store and I want to submit a new version of the app after beta testing. From what I have researched, you can add another submission to the app, and publish it to the store. Then when it's in the store, I'm able to define the visibility of the app. This link is where I get this information. But, if I do this, does this mean that the previous submission is now null and void and can't be found? I think that would be the case? Is there no way to beta test the new version of the app without taking the current version out of the store? Is it recommended to upload a new app named "Blah Blah Beta" and then create a new submission on the original app after the beta gets the okay?
I'm used to iTunes connect and how they do the beta testing, so I'm not sure of the proper protocol in the Windows Dev Center. iTunes Connect you're able to have the current version in the app store, and upload new builds that can be tested.
I hope someone can clarify this for me
Thanks in advance.
My Chrome extension was taken down from the webstore after a copyright violation complain. I tried reaching the complainant and sorting out the matter but he is not responding.
I am contemplating launching a new copy of the extension but I don't want to lose my existing user base. Is there a way by which I could notify the existing users to install the new version?
Getting a list of users to send a mass email or a mechanism to notify them from the official site would do.
When there is an update available in store. If you click on the app it opens an information page where you can see the changelog for the current version of app. Some developers provide this information some doesn't. I wonder where is this information is written in app code. Is it app manifest file ?
To remind again, i don't mean in store description.
There's no built-in way to store/display a changelog. The changelog you see in some apps is handled manually, like you would do to display any other kind of information.