Re-using the same local sync folder fails

[jnweiger]

Seen with OpenCloud Beta OpenCloud Beta 3.0.0.1814 (downloaded from CI)

With owncloud 2.0.0 my configuration used the local sync folder ~/oc.jwqa.de-admin
Now I am upgrading to the current beta of 3.0.0 and don't want to re-download all the files.
I want to continue using the local tree that I already have.

Thus I open advanced configuration and specify the existing ~/oc.jwqa.de-admin as the sync folder.
This leads to an error:

----

The button "Verwerfen" does not help. The error disappears temporarily, but reappears, when I try to start syncing, when clicking "Beenden".

Expected behaviour: There are two buttons: "Use this directory" and "Use a different directory"

Manual workaround attempts:

• rm ~/oc.jwqa.de-admin/*/.sync_journal.db (one db file in each space, none at toplevel) -> no change, the message remains.
• rm -rf ~/.config/OpenCloud* -> no change, the message remains.
• rm -rf ~/.oc.jwqa.de-admin -> now the message disappears. And I can start syncing. BAD: it is now a full re-download.

The wording of the error message makes me double check, if the old 2.0.0 desktop client is still running. It is not. It should not say "is already in use by ..." --- in this case, it should better say "was used by ..."

The internal name "eu.opencloud.desktop" is not very helpful here. I wonder, if that name changed between 2.0.0 and 3.0.0 -- or does the client simply not recognize its own name here?

It remains unclear, how a full re-download can be avoided when updating the client to a new version.

[TheOneRing]

The beta uses a different profile.

[Danie10]

Just want to add I have the identical issue but with v2.0.0.838 after an AppImage update. It asked me to login and reauthenticate again after the update which I thought was odd.

[TheOneRing]

Just want to add I have the identical issue but with v2.0.0.838 after an AppImage update. It asked me to login and reauthenticate again after the update which I thought was odd.

We didn't provide an AppImage update yet?
You would only be able to update to a beta or rc build?

[Danie10]

@TheOneRing thanks yes I tracked down my backup of the old config file and it says beta. No idea why GearLever decided today their was an update. I may have in fact then gone back to an older version. I'm sure if I but it back at beta it will be fine .