You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Is there a public method to determine if there is a new Binary version available? When checking for an update, the console logs An update is available, but it is targeting a newer binary version than you are currently running.
but the calls internally appUpToDate();
I would like to send the user to a URL to download the new binary version
Additional Information
cordova-plugin-code-push version: 2.0.1-beta
Cordova version: 6.4.0
Does this reproduce on a simulator, or only on a physical device? Both
The text was updated successfully, but these errors were encountered:
Hi @jgkinnear, that a good question. Currently we do not have an API method to verify this.
So probably you could try to do one of the following things to get your requirements:
Add an additional callback function to checkForUpdate method and rise this callback e.g. after this LOC. If you could create a PR that implements this and update docs - that would be much appreciated.
You could try to import some stuff from cordova-plugin-code-push, say you need to import class Sdk and class LocalPackage and try to write you custom function reflecting the same logic we do in checkForUpdate method. So this way you should be available to implement your custom handling there.
Please let us know if you have any questions regarding this.
Description
Is there a public method to determine if there is a new Binary version available? When checking for an update, the console logs
An update is available, but it is targeting a newer binary version than you are currently running.
but the calls internally
appUpToDate();
I would like to send the user to a URL to download the new binary version
Additional Information
The text was updated successfully, but these errors were encountered: