search

dani-garcia / vaultwarden

Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
GNU Affero General Public License v3.0
36.78k stars 1.79k forks source link

No syncing on Android 9 #923

Closed almanzarj closed 4 years ago

almanzarj commented 4 years ago

I am having an issue on Android 9 using Samsung Galaxy S8+ with Bitwarden version 2.3.1 Android App.

I have tried uninstall app, install app, clear cache, log out and login.

When I try to do sync vault now...I get error Syncing failed message. I also tried to sync using LTE and WIFI

b-sarrazin commented 4 years ago

Same issue with Android 9 since the last update of the mobile application.

sven-petersen commented 4 years ago

I had this issue with an installation on Home Assistant. I exported my vault and reinstalled the addon (which uses bitwarden_rs). Now it works again. Probably something got corrupted somehow.

deeztek commented 4 years ago

Try this.

Exported my vault to .json. Then I did a search for the following:

"username": null, "password": null

Then in the web browser, I located the particular entry and deleted it.

Not sure which entry it was, but after deleting 27 entries, the android app started syncing again.

pltanton commented 4 years ago

Got the same issue. I found in export that I have multiple (like 7 or so) equal entities with same name and empty fields (each field was empty). It appears after some weird exceptions in desktop client.

Delete of these entities solves the problem. Guess it kinda bag with fresh desktop client.

oooh-name commented 4 years ago

Try this.

Exported my vault to .json. Then I did a search for the following:

"username": null, "password": null

Then in the web browser, I located the particular entry and deleted it.

Not sure which entry it was, but after deleting 27 entries, the android app started syncing again.

@deeztek Thank you!!!!!broooooooooo, you save my day!

dani-garcia commented 4 years ago

I think this is probably related to https://github.com/dani-garcia/bitwarden_rs/issues/921, but if not there's the workaround explained above, so closing the issue.