Before actually deleting files on the underlying file system, the openCryptoFile is removed from the (path, file)-mapping. Additionally, the currentFilePath object is null'ed, to indicate the openCryptoFile should not be used anymore. The usages of currentFilePath are updated to be null safe.
Note, that this only fixes a "symptom", there is still surface for bad timing. The root cause is described in #171.
Fixes #170.
Before actually deleting files on the underlying file system, the openCryptoFile is removed from the (path, file)-mapping. Additionally, the
currentFilePathobject is null'ed, to indicate the openCryptoFile should not be used anymore. The usages ofcurrentFilePathare updated to be null safe.Note, that this only fixes a "symptom", there is still surface for bad timing. The root cause is described in #171.