Recommended patch release flow
The standard flow for publishing a hotpatch has three steps. Following this flow helps to reduce risks.
The standard flow is: Offline testing -> Phased release -> Full release.
Offline testing
Use debugging tools to test the patch. For more information, see Test a patch.
Test the patch offline on popular mobile phones, covering as many device models and ROMs as possible.
NoteIf you do not have enough offline devices, use the EMAS Mobile Testing product for offline testing.
Phased release
Use the hotpatching feature to perform a phased release in three stages. Release the patch to 1%, 5%, and then 20% of your devices. Monitor the following metrics:
Patch effectiveness rate: The percentage of devices that successfully loaded the patch after downloading it. This rate should be higher than 70%.
Patch purge rate: The percentage of devices that automatically purged the patch after downloading it. This rate should be lower than 2%.
A startup crash on a device triggers a protection mechanism that automatically purges the hotpatch.
Crash rate: Use EMAS Crash Analytics to monitor app crashes after you publish the patch. The crash rate should not increase.
Full release
If the data from the phased release meets your expectations, perform a full release.