This repository has been archived by the owner on Oct 1, 2018. It is now read-only.
Fix race condition and android bugs resulting in an incomplete/corrupted installation #44
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.
This will make sure the www folder is never left in a corrupted state. If it is corrupted, it will always be recreated on app start. See: #43
Also once I added logging, I noticed a race condition with two installations being started concurrently, and interfering with each other's files.
I noticed that two calls were being made to the
install
method, and because isInstalling was set from within the thread, both installs would start concurrently. See the small fix in UpdatesInstaller.java.The two threads would then compete over the
www_backup
folder, and in my app's case, this would always fail the update because I have a lot of files in the app and file system errors would occur as the two threads were deleting and creating the same files. I believe this was probably the root cause of issue #43, but the strengthening added for that doesn't hurt either.