Three more requests:
1.) In SeaDrive 1.x, a double-click on the systray icon brought up the virtual drive S:\ In 2.0, this does not work anymore. Could you add it back?
Even after a reboot/reinstallation, it stays like that. You need to go in %userprofile%/seadrive_root and delete the folders.
Wouldn’t it be better to rename the folders than to create new ones?
3.) The transfer progress window is missing a time/date column. IMHO, a time/date column helps troubleshooting when things go wrong as wel as general transparency. In the same vein, I would be great if this window would show more than a maximum of the last 11 uploaded/downloaded elements. (Size adjustable columns would also be great.)
This is the same thing as 2. in my post above. Go to %userprofile%/seadrive_root and delete the account.
This said: I agree, the user accounts shold be deleted when uninstalling the client. At the very least, the admin should be asked what to do with them.
What operations did you exactly do? Do you mean deleting files in seadrive 2.0 doesn’t actually delete them on the server? Do you have relevant logs when this happened?
I think this may be related to unexpected exit of seadrive, perhaps caused by a crash. Usually the program remove the entry in Explorer after it exits. Do you have any files under C:\users\username\seadrive\logs\dumps?
Funny. Came here to ask if you were working on utilizing this Explorer API that OneDrive for Business also uses and came past this thread. So happy to see this! Thanks.
i tested the new client on my Windwos 10 machine (Version 1909). I deinstall the old seadrive (latest seadrive v1) installation before, install the new one (Version 2.0) and restart the pc.
I’ve selected “Always keep on this device”, later I’ve tried to update file locally and it stays in “sync” mode forever.
I’ve tried to logout / login (with and without clear cache)
After logout, seadrive_root\fca050ce\My Libraries\test folder is not accessible any more (access denied).
Only solution I’ve found is to open Explorer.exe as admin, remove test folder, and start SeaDrive/login again. But problem reappears.
[05/09/20 11:36:21] All events are processed for repo 05562368-2e99-4b1b-ad48-5af6f4afca81.
[05/09/20 11:36:21] Repo 'desktop' sync state transition from 'committing' to 'synchronized'.
[05/09/20 11:37:18] SQL error: 19 - UNIQUE constraint failed: CachedFiles.repo_id, CachedFiles.path
: INSERT INTO CachedFiles (repo_id, path, mtime, size) VALUES ('fe28e3df-5b5e-4b3e-845d-540a2d7cb2e0', 'cloud.zip.sha1', 1589010113, 128)
[05/09/20 11:37:39] Repo 'temp' sync state transition from 'synchronized' to 'committing'.
[05/09/20 11:37:39] All events are processed for repo a145b22e-663a-482d-b536-d51bbda150b8.
[05/09/20 11:37:39] Repo 'temp' sync state transition from 'committing' to 'uploading'.
[05/09/20 11:37:39] Upload with HTTP sync protocol version 2.
Is it possible to link the seadrive as a normal network drive/share as the 1.x version would normally do?
Basically the same as you would link a samba share.