OxDrive sync to account breaks repeatedly (on Windows)

I have the following recurring problem with OxDrive:

* upon startup it prompts me to do set up again, but I can't use my account, because it's already in use

* OxDrive is also paused permanently

* when I check, my account is showing up correctly as active account, but even if I resume, instead of the `X GB / Y GB used` it just shows `---` and it is still paused even after resuming pause

So it seems that the connection to my account is somehow broken. One (temporary) fix I found is removing and readding the account, but this also changes the storage location on my PC e.g. to OxDrive (2) and it seems impossible to select the old storage location again. If I select for example `C:/foo/bar/Ox Drive` it instead selects `C:/foo/bar/Ox Drive/Ox Drive`. As a result, all links to the old folder break e.g. start menu items where I pinned a folder. Also I have to move my data to the new location to not lose changes. This is quite problematic and it seems likely I can mess up and lose data, e.g. if I was making changes to the files from multiple devices, it would be hard to figure out, which ones are the correct ones now.

Also most importantly that fix isn't permanent. I did all of that and it broke again with the same issue. This makes the drive functionality unusable for me, as having the drive on the PC is a core feature I need.

I can point to some improvements I would like to see in the Ox Drive software, if that is helpful at all:
* in setup selecting the account that was already set up should be handled cleanly by Ox Drive instead of showing a user error (so basically "idempotency") e.g. remove and readd the account but keep the storage location - then I would not have the issue I mentioned

* the dialog to select the local folder location should actually allow me to put a path, so I get the path that I select and not one that Ox Drive makes up after I pick... then I could just reconnect my account to the existing storage location at least

* there seems to be some underlying issue why this breaks... maybe check recent updates on your side? The issue started for me a few days ago

Cheers,

Philipp