-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fail Sync at create a SecureNote #4590
Comments
I'm not sure what you expect here. You mentioned it was solved and now open a ticket again. Please elaborate what your reason is. Also, this is missing a lot of info which was discussed in that discussion. |
im reporting a bug(?) i create a Secure Note then the sync stop working i explain in the in the discussion. |
Maybe it's not the place to report a bug and it's my fault. |
Via which client, os, browser, phone etc.. please provide that kind of information |
according to #3580 it seems that vw (or the client) sometimes stores (or sends):
A solution was also suggested #3580 (reply in thread) |
@tessus but it would be good to know which client, what fields are filled which are not etc.. else is hard to reproduce if at all. It also might be something in between for example. Nothing to do with either Vaultwarden or Bitwarden even. |
in my case ocurred with android client and with the chrome plugin, the bitwarden windows app work fine |
I used the android client just right now to add a secure note, and it sync's just fine afterwards. If you can reproduce this every time, then there must be something strange in between which causes the json to be changed? Can't be the database engine since that doesn't do anything special with json, and i use the same type. |
Timeline: After 1 or 2 days I realized that my devices were not syncing. Then I created the ticket, and it lasted as long as the ticket and the discussion lasted until the resolution date. As soon as I realized the problem, I deleted the secure note with the key, and it worked perfectly again idk ¯_(ツ)_/¯ |
But, does it happen again if you create a new secure note? |
It might be that some clients send wrong data, but in my memory that was only with very old clients and a buggy. Further could you check if there are more items like that. SELECT * FROM ciphers WHERE atype=2 AND data LIKE '%"Type":null%'; If that returns one or more rows, then try to execute this query after making a backup of the database: UPDATE ciphers
SET data = REPLACE(data, '"Type":null', '"Type":0')
WHERE data LIKE '%"Type":null%'; |
I had this very same issue. Sync stopped working for both Android and iPhone client, I got one hit with the above query and I looked into my Securenotes and had one item created at that exact |
Collections were not visible in the organization view. This was because the `flexibleCollections` was set to `true` Found an issue with loading some old created Secure Notes which had `{}` or `{"type":null}` as there `data` value. This isn't allowed. When detected, replace it with `{"type":0}` Fixes dani-garcia#4682 Fixes dani-garcia#4590
Collections were not visible in the organization view. This was because the `flexibleCollections` was set to `true` Found an issue with loading some old created Secure Notes which had `{}` or `{"type":null}` as there `data` value. This isn't allowed. When detected, replace it with `{"type":0}` Fixes dani-garcia#4682 Fixes dani-garcia#4590
Discussed in #4554
This discussion a bug and i think this must be reviewed (read the last discussion comment)
Originally posted by Crosus97 May 15, 2024
Subject of the issue
when press de sync button apper a Fail Sync Error, that work until 3 o 4 days, no changes are made it
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
Steps to reproduce
I now detect than randomly sync, i think where the password must be sent on a field, the plugin automatically sync the database,
Expected behaviour
the plugin database must be synced
Actual behaviour
apper a sync error
Troubleshooting data
The text was updated successfully, but these errors were encountered: