You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android will see the new entry. If not automatically it should at least show up after a manual sync.
Actual Result
The entry will not show up until logging out and back in again. A manual sync doesn't help.
Screenshots or Videos
No response
Additional Context
I took look at the communication using tcpdump+wireshark and it looks like the only thing Android ever does is poll GET /accounts/revision-date.
That date does not change after creating a new password though.
I assume that unlike desktop, Android uses the date exclusively to decide if a sync is needed. So since that's never being updated by the server you'll never see any updates until you log out and back in again.
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
When the user is not part of an organization,
`UserBumpAccountRevisionDateByCipherIdQuery` doesn't work. In that case
we have to use `UserBumpAccountRevisionDateAsync` instead.
This was already done by most parts of the code but a few more were
missing.
Fixesbitwarden#2615
When the user is not part of an organization,
`UserBumpAccountRevisionDateByCipherIdQuery` doesn't work. In that case
we have to use `UserBumpAccountRevisionDateAsync` instead.
This was already done by most parts of the code but a few more were
missing.
Fixesbitwarden#2615
M1cha
added a commit
to M1cha/bitwarden-server
that referenced
this issue
Feb 2, 2023
When the user is not part of an organization,
`UserBumpAccountRevisionDateByCipherIdQuery` doesn't work. In that case
we have to use `UserBumpAccountRevisionDateAsync` instead.
This was already done by most parts of the code but a few more were
missing.
Fixesbitwarden#2615
…2634)
When the user is not part of an organization,
`UserBumpAccountRevisionDateByCipherIdQuery` doesn't work. In that case
we have to use `UserBumpAccountRevisionDateAsync` instead.
This was already done by most parts of the code but a few more were
missing.
Fixes#2615
Steps To Reproduce
Expected Result
Android will see the new entry. If not automatically it should at least show up after a manual sync.
Actual Result
The entry will not show up until logging out and back in again. A manual sync doesn't help.
Screenshots or Videos
No response
Additional Context
I took look at the communication using tcpdump+wireshark and it looks like the only thing Android ever does is poll
GET /accounts/revision-date
.That date does not change after creating a new password though.
I assume that unlike desktop, Android uses the date exclusively to decide if a sync is needed. So since that's never being updated by the server you'll never see any updates until you log out and back in again.
Githash Version
3997def-dirty
Environment Details
mariadb container: https://github.com/M1cha/homeserver/blob/284054030b76e8faf4a3b5749e491157b6623c55/files/containers/bitwarden-mariadb.container
bitwarden container: https://github.com/M1cha/homeserver/blob/284054030b76e8faf4a3b5749e491157b6623c55/files/containers/bitwarden.container
Database Image
docker.io/mariadb:10
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: