Fixes thread safety issues in android code. closes #161 #165
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.
Before, every call from flutter was executed in a separate thread and only the ensureInitStorageCipher was synchronized. All other operations were run without any synchronization. Most of the code is not thread safe, which caused multiple problems when two or more method calls happened to run at the same time.
This PR fixes the thread safety issues by using a single worker thread in which all calls from flutter are executed.
This closes #161 but probably also fixes #163.