An opk that had beta features, but has the same version number as the one that’s currently live to the public was uploaded for release to the testing channel on release management. However, after it was done processing, we did NOT roll it out and instead removed it.
Then, new users, that did not have Overwolf preinstalled, who installed our app via our app installer on our page Insights Capture - Record & Review Made Easy, had the opk with the beta features added instead of the public version.
I think the same version on both the beta test opk and public opk caused this issue, but since we did not roll out the beta opk, it should not have been available for the public to download, and it was uploaded and processed on the testing channel on Overwolf console release management.
Can you reproduce it (exact steps to reproduce):
- upload a different opk, but with the same version as the public to a testing channel on overwolf console, but do not roll it out and remove it after it’s done processing.
- As a new user who does not have Overwolf installed, install the app using the respective app’s installer file, not through the Overwolf app store.
- The new user should have the opk that was uploaded by not rolled out.
Impact for my app: [e.g. x% of the users complained about it, it’s a show-stopper]
show-stopper, but an easy fix is to version bump the opk meant for the public.
Do you currently have a workaround?
Version bump the opk that was meant for the public.
Please reproduce and attach a zip package of your OW client logs
In the InstallerTrace, the line 12/05/2022 11:32:14.116 shows app link being downloaded.
Log (2).zip (43.1 KB)