Problems with v3.0.0-beta.1 on MacOS

[windsource]

I have been using the v2.0.0 arm64 on MacOS before. Today I have downloaded thev 3.0.0-beta.1. After installation it did not remember the previous settings so I have entered my server URL again and authorized the app. Then I have given it the same local path with the existing sync as I thought it could re-use the existing files. But it did not recognize the existing files and created ...(2) files instead. So I stopped the sync and have set it up to use a new folder. Then the sync of my personal folder and the spaces started. It looked like as if the sync worked and has finished so closed the lid of the MacBook. When I opened it again after an hour I got a message that the app has crashed and I started it again. It did not recognize the previous sync and started to sync all folders again.

[TheOneRing]

Hi @windsource you are right the config is not reused but that's on purpose.
As we don't support downgrades, switching from a 3.00 pre-release back to a stable release would not be possible.
Therefore, we decided to make the preview clients use an independent configuration, they can also run in parallel with a production client.
The beta client also has asserts enabled so it might crash occasionally, if it does, please open a bug report, the reason for the crash will be in the log file and in "$TMPDIR/OpenCloud Beta-crash.log".

I will update the release notes to communicate those changes.

Tanks for testing!

[windsource]

Hi @TheOneRing, thanks! As the crashlog contains some sensitiv information, I have sent it to you via email.

[windsource]

I just wonder how to run the beta in parallel to a production client? After I installed the beta, the v2.0.0 app was not available anymore.

[TheOneRing]

I just wonder how to run the beta in parallel to a production client? After I installed the beta, the v2.0.0 app was not available anymore.

Ouch, you found your first beta related bug, but your profile won't be affected so switching back to production builds won't be affected.

[TheOneRing]

Hi @TheOneRing, thanks! As the crashlog contains some sensitiv information, I have sent it to you via email.

Thank you for the report. It was a well known assert that wasn't too important, and I decided to just remove it.
5e76f18

I guess I'll build a beta two tomorrow. Thx for the reports.

[jnweiger]

related: #681