fix: Fix cancelling installation by not prematurely deleting patched APK #2490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue had been caused by a race condition in asynchronous processing.
In
setLastPatchedApp()
method,await
keyword was needed beforedeleteLastPatchedApp();
A code to reproduce:
The code is executed in the order (1) → (2) → (3) → (4) → (5).
As a result,
lastPatchedApp.apk
is sometimes randomly deleted after copying is succeeded.Conclusion
The
deleteLastPatchedApp()
calling insetLastPatchedApp()
is unnecessary from the beginning, so this PR removed this.Because
lastPatchedApp.apk
and a pref will be overwritten without callingdeleteLastPatchedApp()
.The calling in
reAssessPatchedApps()
is also redundant because the file does not exist, so removed.