-
-
Notifications
You must be signed in to change notification settings - Fork 170
Description
Please agree to the following
- I have searched existing issues for duplicates
- I agree to follow this project's Code of Conduct
Summary
Wrong access to files when a connection has been removed and another connection added of the same type
System Setup
- Android: X
- Cryptomator: YCloud Type
No response
Steps to Reproduce
- Add a cloud connection of type a
- Browse files using this cloud connection
- Remove this cloud connection
- Add another cloud connection of this type a (make sure that you don't kill the app after deleting the cloud)
- Browse files using this new cloud connection
Expected Behavior
Files of the new cloud connection are shown
Actual Behavior
Files of the deleted cloud connection are shown
Reproducibility
Always
Relevant Log Output
No response
Anything else?
The reason for this is that when browsing a cloud connection, an entry is created in a map of the DispatchingCloudContentRepository, when a cloud connection is removed in the database using the CloudRepositoryImpl, the entry in the DispatchingCloudContentRepository isn't removed. This is fixed in 85c0658 by updating the entries in DispatchingCloudContentRepository as well when removing a cloud in the database.
As the DispatchingCloudContentRepository is in memory, the app must not be killed after deleting the cloud and the files must be browsed with the old cloud connection before it was deleted, otherwise the problem does not occur.