Submitting a new version of your app
Your app is available on the Overwolf Appstore and it's time to release new features you've been working on. That’s awesome! In this article we'll go over the process of submitting updates for your app in a few simple steps.
Submitting a new version
To get the update cycle started, head on over to the developers' console, and select your app. From there, follow the instructions detailed here.
App version review
For the first few versions of your app, an update might need to be submitted for review.
This is done through the developers' console, or through your assigned DevRel manager. The goal is to ensure that your app is in top shape, and that no bugs slip through, as well as give you a safety net for your first few releases, so you can get used to the release process.
Once the review process is completed, you will be able to release it to the public.
After several version reviews, once your app is deemed stable, mandatory version reviews might be turned off. However, it is still recommended, when possible, to send big versions for review even after the fact, to make sure nothing is missed.
Rejected reviews
We want to make sure that your app is running smoothly and that your update works just as well as your original app. If our team spots any issues, we’ll send you a list of them along with feedback, and will help with any issues you have trouble fixing. Once you have fixed the issues that were detailed, you can send the updated version to be reviewed again.
A detailed change log will help our team to identify the changes better and will make the testing process faster.
Deploying app updates
In general, apps are updated automatically every few hours, or when Overwolf is restarted. However, if there's a good reason to "force" an early or immediate update, you can do so.
Use updateExtension() to check the app and perform an update:
Call
checkForExtensionUpdate()
. If there is an available update - register for theonExtensionUpdated
event and callupdateExtention()
.Once the update has completed successfully, the onExtensionUpdated event will be triggered, and you can call
relaunch()
. In case of failure, the callback ofupdateExtention()
returnssuccess:false
.
No app should ever update while it’s being used in-game unless the user explicitly requests it. In fact, there is a failsafe mechanism where this API will only work if a relevant user action is detected, such as clicking a button or otherwise choosing to update.
It is also possible to check the app's current version at any point, by using the getManifest()
method (you can find the current app version under the manifest’s "meta" property).
If the current app version and your server stored version are not identical, you can prompt the user to restart Overwolf to update the app.
However, make sure the version is fully phased before updating your servers, to avoid an infinite update loop.