Preface
Compared with h5, app has the characteristics of update delay and difficulty in update. After deploying updates, h5 can ensure that all users access the latest functions, and app may have multiple versions, and users can choose not to upgrade and continue to use it;
However, sometimes, the app has undergone large-scale adjustments, which has resulted in the unavailability of all previous versions of the app, or some important functions have been adjusted (such as the charging content has changed), and forced users to update the app, which is not uncommon;
Therefore, in the first version of the app, the update function in the package should be added to ensure the update battery life of the app.
Complete package updates and hot updates
The updates of the APP are divided into whole package updates and hot updates.
The whole package update refers to downloading the complete apk file for overwriting and installing.
Hot update refers to packing the app where changes are made into a wgt file, only updating the contents in the wgt file, and not installing the entire package. From the user's perspective, it is also called traffic-saving update.
Version number constraints
Since it is a version update, leave the constraints of the version number.
Because there are two update methods, the version number specification must be formulated first:
Suggestions: Strictly followSemantic Versioning 2.0.0Semantic version specification.
Major version number: Incompatible API modification
Secondary version number: new functionality that is backward compatible
Revision number: Backward compatibility issue fix
Implementation principle
- Develop background version management functions, upload the Android installation package every time the release version is recorded, whether it is a hot update or a whole package update, whether it is a forced update, etc.
- Every time you open the app (onLaunch life cycle), request the latest version information through the interface, and then obtain the current installation package information, and compare the version number.
- If the version number is inconsistent and the version number obtained by the interface is greater than the version number of the current application, a whole package update or hot update is performed.
- It should be noted that there is no such operation as downloading and installing the installation package in iOS, so on the iOS platform, you need to jump to the appstore for updates.
export default {
onLaunch: function() {
// Conditional compilation, update operations only in the app environment // #ifdef APP-PLUS
if (.NODE_ENV === 'production') { // Only enabled in a formal environment to avoid updates affecting the development and testing environment (this step depends on your needs)
// Get app running information (, function(widgetInfo) {
// Get the latest version information through the interface, and the specific request will not be demonstrated. getVersion({
platform: '1'
}).then(res => {
if (!res) {
return;
}
// The version number gets a string similar to '7.0.1', remove it. and convert it to a pure number const appCode = parseInt(res.app_code.split('.').join(''))
const version = parseInt(('.').join(''))
if (appCode > version) { // Only the interface version number > current package version number will be updated // The type is 0 hot update (see interface design) if ( == '0') { // Hot update, download update file. In this step, you can first display the ui for the update prompt. The user clicks to update before downloading the update. (res.download_url)
} else if ( == '1') { // The entire package is updated. In this step, you can first display the ui for the update prompt. The user clicks to update and then downloads the update. (res.download_url)
}
}
}).catch(err => {
(err)
})
});
}
},
methods: {
// Complete package update updatePackage(url) {
// iOS platform does not allow this update, so we need to jump to the appstore for update if (().platform === 'ios') {
({
action: 'itms-apps://xxx' // Link can be obtained through the interface });
} else {
= true
// The download task was built, but the download was not started at this time const dtask = (url, {},
(downloadResult, status) => {
if (status === 200) {
(, {
force: false
},
function() {
(); // Restart after successful installation },
function(e) {
({
icon: 'none',
title: 'Download update failed'
})
});
}
}
);
// Execute the installation package download ();
}
},
// Hot update updateHot(url) {
({
url,
success: (downloadResult) => {
if ( === 200) {
// Install after downloading the update file successfully (, {
force: false // Whether to force installation, if the version number of the application to be installed is not higher than the version number of the existing application, the installation will be terminated and the installation will fail. },
function() {
({
title:'Update is completed, and will be restarted soon',
icon: 'none',
position: 'bottom'
})
setTimeout(() => {
(); // Restart the application after installation },2000)
})
}
}
});
}
}
}Other solutions
The plugin market providesuni-upgrade-centerThe upgrade plan includes the logic of backend management app version and automatic app update. It should be noted that backend management is a plug-in based on the uni-admin framework. If uni-admin is not used in the application, integration will be relatively troublesome.
References
uni-app resources online upgrade/hot update
Summarize
This is the article about the forced updates and hot updates of uniapp development APP. For more relevant uniapp APP content, please search for my previous articles or continue browsing the related articles below. I hope everyone will support me in the future!