-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bcc_self
is reverted to 0 after upgrade of existing multi-device setup
#6432
Comments
Migration in #6344 inserts Maybe the migration should have been |
Unless someone finds other reasons for why this could have happened, I suggest we copy the migration, but now with |
We don't have a clear way to reproduce it and it does not seem to happen to any of developers, so maybe it's a rare case. I upgraded all my devices to the latest core and don't have this bug. Since |
Replaced with #6433 |
I think this might happen because of the bug in the migration, it should actually be "INSERT OR IGNORE INTO config (keyname, value)
SELECT 'bcc_self', '1'
FROM config WHERE keyname='delete_server_after' AND value!='1' instead of |
…=1 (#6432) Users report that in a setup with Android (1.50.4 from F-Droid) and Desktop (1.48.0 x86_64 .deb release) and chatmail account `bcc_self` was reverted to 0 on Android, resulting in messages sent from Android not appearing on Desktop. This might happen because of the bug in migration #127, it doesn't handle `delete_server_after` > 1. Existing chatmail configurations having `delete_server_after` != 1 ("delete at once") should get `bcc_self` enabled, they may be multidevice configurations: - Before migration #127, `delete_server_after` was set to 0 upon a backup export, but then `bcc_self` is enabled instead (whose default is changed to 0 for chatmail). - The user might set `delete_server_after` to a value other than 0 or 1 when that was possible in UIs. So let's add another migration fixing this. But still don't check `is_chatmail` for simplicity.
Some migrations change the `config` table, but they don't update the cache. While this wasn't the cause #6432, it might have caused a similar bug, so, let's clear the config cache after every migration.
Users report that in a setup with Android (1.50.4 from F-Droid) and Desktop (1.48.0 x86_64 .deb release) and chatmail account
bcc_self
was reverted to 0 on Android, resulting in messages send from Android not appearing on Desktop. The setting is not displayed on Android for chatmail accounts, but as a workaround, exporting a backup on Android and immediately destroying it worked. Upgrading Desktop to 1.50.1 did not result inbcc_self
reverting there to 0.The problem was likely introduced in #6344
This change is part of core 1.153.0. Android 1.50.3 uses core 1.152.0 and Android 1.50.4 uses core 1.153.0. Desktop 1.50.1 still uses core 1.152.1, this is likely why the problem did not appear there yet, it may still revert to
bcc_self=0
after upgrade.The text was updated successfully, but these errors were encountered: