You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scoped storage FileZilla rare dir duplication bug: #205 (comment)
Problem
Normal checks like exists() do not work here. Last modified time also doesn't work here. Not even findFiles() does anything to help here. Found only one thing that works, but as noted with the 1st edit below, it has increasingly hacky problems.
FileZilla with 2+ connections on transfers will get into a state where at least 2 connections try to make the same dir. Because the normal checks fail to work here, it creates an empty duplicate with (1) added on. More connections, faster the problem shows up.
Notes
Its technically probably either half a DocumentFiles/DocumentsContract bug and/or half a FileZilla bug. It should be fixed there.
Everyone may have a differing opinion of where it should be dealt with.
Edit - Realized late that I know some people will have duplicate dir names end with eg (1) already for real so... had to make a change to check that too. Needs more testing.
Edit 2024 Dec
Testing did not go well. Going to be a while, if its even possible. I now have zero confidence in getting this fixed here. Best to just restrict FileZilla to only 1 connection or use WinSCP instead as that doesn't have this problem. Will keep an eye on it as time goes by. I'm not thrilled by it getting more hacky so might not try any further. Don't know what else to do about it as normal things don't work.
The text was updated successfully, but these errors were encountered:
Xavron
changed the title
Scoped storage FileZilla dir duplication bug (under testing)
Scoped storage FileZilla dir duplication bug
Nov 10, 2024
Scoped storage FileZilla rare dir duplication bug: #205 (comment)
Problem
Normal checks like exists() do not work here. Last modified time also doesn't work here. Not even findFiles() does anything to help here. Found only one thing that works, but as noted with the 1st edit below, it has increasingly hacky problems.
FileZilla with 2+ connections on transfers will get into a state where at least 2 connections try to make the same dir. Because the normal checks fail to work here, it creates an empty duplicate with (1) added on. More connections, faster the problem shows up.
Notes
Its technically probably either half a DocumentFiles/DocumentsContract bug and/or half a FileZilla bug. It should be fixed there.
Everyone may have a differing opinion of where it should be dealt with.
Edit - Realized late that I know some people will have duplicate dir names end with eg (1) already for real so... had to make a change to check that too. Needs more testing.
Edit 2024 Dec
Testing did not go well. Going to be a while, if its even possible. I now have zero confidence in getting this fixed here. Best to just restrict FileZilla to only 1 connection or use WinSCP instead as that doesn't have this problem. Will keep an eye on it as time goes by. I'm not thrilled by it getting more hacky so might not try any further. Don't know what else to do about it as normal things don't work.
The text was updated successfully, but these errors were encountered: