I’ve been looking into this further, and I’m getting this error on some map files that are open in a mapping application. These files haven’t changed in years, the modified date is years in the past, and the date and size are the same on drive.google.com as they are on my disk, and yet insync is complaining that it can’t modify them.
Is it possible that either (a) insync opens files for writing even before it has determined that they are changed and require writing? … or… is it possible that insync’s way of determining a file needs changing (writing) has some issue? (How does it determine that?)