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.
Related
About 5 days ago my app passed 570 downloads but my badge still shows 100 downloads on google play, Isn't 5 days too long to update these stats?
They are supposed to update every 24 hours., stats which is displayed in developer console is not reliable, they often stop updating for few days.
I'd suggest you to integrate Google Analytics for Mobile, localitics or any other framework if you want good statistics.
I had the same problem recently so I contacted Google Play developers support and they clarified the issue.
As it turned out, the number shown in Developer's console statistics "New users acquired" and on the "Installs" badge in Google Play are computed using different algorithms. The first one shows raw installs while the second one shows the somehow corrected data. In particular, install metrics may be discounted or even removed entirely if Google detects fraudulent installs.
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.
As you know Firefox extensions can get broken when newer versions of FF are released, i.e. Firefox makes changes to extension requirements.
Is there a list/resource/forum board etc, that describes what these changes are?
Especially since many of the "getting started" tutorials were written along time ago. now it is hard to know which requirements have changed and which are still the same.
Each significant update is listed in the release notes for developers at https://developer.mozilla.org/en-US/Firefox/Releases. This includes information for web and add-on developers.
The best way to stay up-to-date is to follow the blog at https://blog.mozilla.org/addons/, which frequently publishes about changes affecting Add-on compatibility, AMO statistics and so on.
So far they're the only people I can find that are doing a chart control...
What happens when the beta expires? How does it expire? (Does it expire?). They look great but there is no pricing information or expiry information.
Here is a direct quote from the EULA:
“You may distribute the Programs as embedded in Your Integrated Products to Your end-users only pursuant to an end-user license that meets the requirements of this Section.”
So, yes, you can ship Apps built with Telerik Windows 8 Controls Beta to the Store.
"Beta," by definition, suggests not ready for production use.
There are at least a couple of things you should think about before moving forward:
Does the license agreement for the controls allow use in a production app (you did read the license, right?)
Are you willing to risk the possibility that the app might suddenly stop working for any and all users who have downloaded it, until such time as you replace the controls with working versions (and get the updated version of your app submitted to the store)?
As long as the controls fit the Windows 8 app design, and don't cause performance or crashing issues, they may not have any impact on whether or not the app gets through certification.
But the larger issue is one of risk. Betas are for testing. IMO, unless the beta includes a "go-live" license, you should probably stick with using beta software for evaluation and testing only.
To be clear, that's no knock on Telerik's beta quality (or anyone else's, for that matter). Just a reminder that beta software isn't finished yet.
Let me clear what I mean. I’ve published on marketplace the app in version 1.0. Now I want to update my app to version 1.1. I wrote a method which should be called only when the app is updated from 1.0 to 1.1. When new users will already install the app in version 1.1 from marketplace a method should not be called.
Any suggestion?
EDIT:
I could solve my problem by getting date of app installation. Is there any way to obtain that kind of information in code?
You'll have to manage this yourself.
The simplest way to do this is to store (in IsolatedStorageSettings) the current app version number. You then check this when you start and compare it with the current apps version numebr.
If there isn't a value in settings then you know it's the first install.
If the version numbers are different you know the app was updated and you can take whatever action is appropriate as part of the upgrade. (Aside - I always think it's nice when apps acknowledge that they were upgraded.)
There's no way to get the datetime of installation but you could capture the date/time of first run. Just get (and save?) the date/time when storing the version number. Beware that you will be subject to changes in date/time on the device. If you want to use a webservice to get the date/time then you'll have to deal with issues of no connectivity.
I would recommend against trying to determine the version/upgrade based purely on the date/time on the device as there are many possible issues to consider and work around.