We submitted a new add-on some days ago. It is currently under review but this will take some days. On the other hand, it is possible to install the add-on over the app store (with a big hint that it is not reviewed yet).
When we tell our clients to install the unreviewed Add On and the add-on will be approved for example in 2 weeks, will the auto update process work for the users who already installed the add on while unreviewed status?
Yes, the auto update function does work for un-reviewed add-ons (or at least it did the last time I had an add-on in this state). The version that gets reviewed will be the one that is current at the time the reviewer begins reviewing the add-on.
Once the add-on is reviewed, the version to which people are auto-updated is the one which has been most recently reviewed (not any un-reviewed version). Users will generally have the option to manually update to an un-reviewed version which is pending in the review queue. They are not notified that such a version exists. A fully reviewed add-on has the option of having a beta channel which is auto-updated separately.
Related
I've accepted the migration from a personal to a company account.
I was also aware of the Developer Portal being disabled, which I was fine with. I was going to carry on working on features using existing certificates, etc.
However, I have a requirement for Push Notifications, and every time I try to build my app in XCode, I get:
"MyApp (iOS)" requires a provisioning profile with the Push Notifications feature.
And then it failed, preventing a proper build, as well as any ability to further develop.
I am wondering if I am able to disable the requirement for Push Notifications from within XCode, so I can keep working on features that exclude push notifications, or if there's a way to speed up the process? It's been over 12 hours and my Developer Portal still says:
We’re processing your membership migration from an individual to an
organization.
Please note that your membership benefits are temporarily disabled
during this time.
I would just like to do some work. I tried searching for expected processing time for a migration. I searched the internet and apple forums, and only found some old posts, some 12+ years old. Some said the wait is sometimes up to a month, but this was back in 2008, so I hope they've sped it up since then.
I developed a mozilla firefox addon and it passed the Full Review by AMO Reviewers and it is available in the store. Now I provide a new version of the same for update review. How long will this process take?
OLD
From my own experience the update takes a few days (2-5 days), depends on the changes.
Note: The updated version is not visible to the Firefox users until it passes the review.
UPDATE
Mozilla has updated the mechanism for the validation process and now it is automated. Which means the validation takes up to one day but as they mention in their review process after the automated validation a reviewer may examine the code and reject the extension.
It can take anywhere between 10 minutes to 50 days, or longer.
How long it takes varies quite a bit based on the changes you have made, the current status of the queue and the reviewers who are currently active. For a fully reviewed add-on, the minimum time from submitting a new version to approval which I have experienced is about 10 minutes; the maximum was about 50 days. If the changes you have made require an admin reviewer, then it will probably be substantially longer.
Prior to the review being completed, the updated version will be visible on the version history page and can be installed from there (I have directed users to go there to install the new version when I have had a compatibility problem with a new release of Firefox). However, users of your add-on will not be automatically updated to the new version until after it passes review. If the new version of your fully reviewed add-on does not pass review, one option that the reviewer has is to provide the new version with preliminary review status. In that case, your users will not be automatically updated to the new version and the version which will be normally installed for new installations (without going to the version history page) will be the old fully reviewed version.
This question already has answers here:
Disable developer mode extensions pop up in Chrome
(20 answers)
Closed 4 years ago.
Recently Google added this annoying pop up to the dev channel.
Someone answered here (Disable developer mode extensions pop up in Chrome) to edit the chrome.dll to get rid of the pop up.
However, the method described there does not seem to work anymore.
Additionally, it would be nice to have a batch script that patches chrome.dll should Google push a new update.
EDIT: Open to new hacks, since wOxxOm stopped maintaining his useful script (the manual method seems to be outdated as well)
I am adding here the official ways to solve this issue and I know they are not optimal, but it makes sense that these solutions are present here.
The first solution and the most complicated one is to create a Google Store Account and go through all the steps to activate it, with it you can upload your extension package and keep it Private, so you can share the link to this package to who will need to install it, this way that message will never show since the extension has been approved by Google team and it's secure.
The second option is to download the Chrome Dev Browser, linked Here, it wont show on the screen that you are downloading the Dev Channel, you have to trust it is happening. This version of the browser works side by side with the official version so you don't have to uninstall or anything, and all settings are separated so it's really like a different browser.
I am using version 64 of it and it solved my problem with the extension.
If you can't use dev/canary builds the easiest way to remove the pop-up is to package your extension and then use group policies to whitelist it, as outlined here: https://stackoverflow.com/a/38011386/991321
I have the latest update for Nightly (34.0a1 (2014-08-14)). It addressed one of the two problems I have from the previous update, which was the disappearing input fields. The other problem was the shrinking of the Google search field. What can I do to fix this?
See screenshot here.
#Acnologia, we are aware of the issue and have logged a bug with Google for them to fix the issue. You can follow along on here if you need more details.
The way I worked around the problem was to close Nightly, open Internet Explorer, and then re-download Firefox Nightly over the version I already have (DO NOT DEINSTALL!). Apparently it reset the version back to "34.0a1 (2014-07-21)" - before the "Google Search Results Page Searchbar Too Small" issue started. Then each time I start Nightly and Windows7 asks me if I want to allow the application to make changes to my computer, I answer "No" so Nightly does not get updated.
Then, each evening after I get home from work, I Google the past 24 hours to see if the issue has been fixed yet, and I will not update Nightly again until it has.
I realize this is a cheap workaround, and I would love to be able to trust Nightly Updates again, but this common issue should have been foreseen before the build was released. - And I will give them another week or two to figure it out, and if not... bye, bye Nightly!
Google Play Developer Console allows developers to upload a beta APK, and invite a Google Group to use it.
How to know how many users are using my beta?
In the console:
Go to Statistics,
Click Export as CSV,
Uncheck everything but Installs devices current and by app version
In the resulting CSV, spot the id of the APK you sent for beta
The number in the third column is the number of beta users.
The Google Play Developer Console has changed a lot since the original answer.
If you are using Open Beta Testing then go to:
Release Management / App Releases / Manage Beta
and you will see something like this:
Note: if the number of testers is not showing, this might be because the number has not yet reached a certain threshold.
This specifically answers the question "How many people have opted into Beta testing?" which may or may not be what the OP was really interested in.
Analytics would be the way to discover how many are actually using the beta version.