Closed chenxiaolong closed 1 year ago
This bug can only occur once during an upgrade from an old BCR version.
For folks who have already upgraded to the latest BCR, they'll need to manually update the auto-record rules to what they prefer.
The fix for this bug will only apply to future upgrades from versions before 1.42.
The migration logic for upgrades has been fixed in version 1.44. People who have already upgraded to 1.42 or 1.43 before will have to manually update the auto-record rules to their preferred behavior.
From https://github.com/chenxiaolong/BCR/issues/344#issuecomment-1559493596:
This is a bug in the migration logic from the old "Initially paused" setting to the new auto-record rules:
Initially paused
was never changed by the user:Initially paused
was ever changed by the user (even just by turning on and then off):This resulted in the opposite value being used if the user ever toggled "Initially paused".