Fix removeOfflineRecord so that it does not rely on class-level fileDeletion map #513
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.
Using fileDeletionMap with Rx is unsafe
Using fileDeletionMap with Rx is unsafe. Deletion in the current SDK may happen concurrently, e.g.
removeOfflineRecording
anddeleteStoredDeviceData
can be called simultanously, which can lead toConcurrentModificationException
on Android, because one thread can iterate over class-levelfileDeletionMap
while the other modifying it. It can lead to undeterministic behaviours. In general we think it conflicts with the reactive nature of the other features in the SDK to keep a modifiable state variable outside of the reactive flow.Relates to
Additionally: