cryptomator0.log This file is in use , when portable app is in a OneDrive sync folder

[oeloo]

Behaviour

Steps to reproduce this issue

1. Copy Cryptomator portable folder into a OneDrive synchronized folder
2. Launch Cryptomator portable application

Expected behaviour

OneDrive should sync Cryptomator portable folder without issues.

Actual behaviour

After a few minutes, OneDrive has a sync issue due to Cryptomator portable :
cryptomator0.log
This file is in use
This item is open in another program. Close the item to continue syncing it.

Configuration

App release / arch (ex. 1.0.0-2 win64) : Cryptomator Portable

Operating system (ex. Windows 10 Pro 64 bits) : Windows 11 Pro 64bit fully up to date

Note: I have fully read Crytomator website and portapps.io and I have tried:
common:
disable_log: true

as described here: https://portapps.io/doc/configuration/
but it does not change anything to the problem because this is not actually disabling logs.

Note bis: It is an important issue because If a portable version cannot be used in OneDrive, what is the point of having a portable application.

[Mario-Hofstaetter]

Note: I have fully read Crytomator website and portapps.io and I have tried: common: disable_log: true

@oeloo: Did you rename the config file cryptomator-portable.sample.yml to cryptomator-portable.yml as documented?

I just tried this with version cryptomator-portable-win64-1.6.10-10-setup.exe and it works as expected.
When trying with default settings my logfile was named cryptomator-portable\log\cryptomator-portable.log however, not cryptomator0.log

Be sure not to change indentation in the file since this is YAML!

common:
disable_log: true

is WRONG ❗ . It has to be:

common:
    disable_log: true

It is an important issue because If a portable version cannot be used in OneDrive, what is the point of having a portable application.

Onedrive not being able to sync the app logging file while the app runs does not impact cryptomator file encryption (IMHO). This log file is unrelated to your actual vault data. So the onedrive warning is more annoying than severe.

[oeloo]

Onedrive not being able to sync the app logging file while the app runs does not impact cryptomator file encryption (IMHO). This log file is unrelated to your actual vault data. So the onedrive warning is more annoying than severe.

The problem is that you cannot define file exception in OneDrive, so the warning do becomes very problematic (unless your Onedrive storage is very small).

I am quite sure I put a tab as I know indentation in .yml like in Python is important. I have moved to the Windows installer of the app because of the issue described in this thread, so I cannot retest.