Description
After an app is published, developers can no longer modify the released version. If a bug is discovered, the traditional solution is to release a new version of the app. This approach is inefficient and can result in a poor user experience. To address these issues, mPaaS provides several Operations and Maintenance (O&M) solutions, such as switches, H5 offline package publishing, Mini Program publishing, and hotpatching. Note that hotpatching is not yet available for iOS. These methods offer flexible ways to resolve online issues, but they must be integrated and configured correctly.
Scenarios
Use switches to control code execution paths. You can wrap new code or code with uncertain stability in a switch. If a failure occurs online, you can push a switch from the server to disable the faulty code immediately. This push-pull method ensures a 100% real-time delivery rate.
Update H5 offline packages. If a failure occurs in an offline package, you can identify the problem and publish a new version from the real-time publishing console. This push-pull method ensures that the update reaches users immediately.
Update Mini Programs. If a failure occurs in a Mini Program, you can modify and republish it. Similar to H5 offline packages, this method ensures that the update reaches users quickly.
Use hotpatching to resolve online issues only as a last resort. Hotpatching is a native fallback method that works by delivering a hotpatch package to modify and replace problematic app code. Note: This is a high-risk operation. Before you publish the patch package, you must perform strict testing and validation.
