Watchtower upset if folder moved or deleted

Lord_Fluff

Monterey / M1 MacBook Pro / PP2021

Watchtower gets stuck in a pattern of showing this pop-up if a folder is renamed or deleted in Finder

It is impossible to fix and will keep on popping up until PP is restarted

Sir_Ivan

What is full path to moved/deleted folder? If it is ok to post it here.

Lord_Fluff

It will happen with any folder. This spate of errors relates to my main external media drive.

Sir_Ivan

Are you on macOS or Win?

Lord_Fluff

Please see the top of the original post

Sir_Ivan

Got it! Will test on my side, if won't be able to replicate I will make a debug version for you.

Lord_Fluff

On restarting PP the same error box pops up, but with the missing folders actually named - at this point is IS possible to fix the linking issues such that the box doesn't keep popping up again

Sir_Ivan

Can not reproduce on my side. I will prep debug version and send it to you. I believe I have your email Lord Fluff.

Lord_Fluff

Just to elaborate - Watchtower is only mapped to one high level folder, the folder which is moved or deleted is always several folders deep within that. Auto sync is set to on.

One idea might be that the folder is moved/deleted/renamed at the same point Watchtower is doing an autosync.

A Mac friend couldn't replicate it either, but didn't try with deep folders, and he's also on an Intel Mac

Sir_Ivan

Good note, I will test deep folders as well!

Lord_Fluff One idea might be that the folder is moved/deleted/renamed at the same point Watchtower is doing an autosync.

I think, because of how code is written, this one shouldn't be a problem.

Lord_Fluff

It might also be worth mentioning that the master folder syncs to the Mega cloud, so the changes in the folders come from there, and are then reflected in the local drive, which Watchtower then gets confused by.

I've previously given up on Watchtower when I was using Google Drive due to the creation of a dozen references to the same file being created - I don't have this problem with Mega, but maybe this is related?

Sir_Ivan

This might be the reason. Let's see what debug version will show us.