Closed deeztek closed 4 years ago
I experience same issue. Last sync was successfull at 29th february. I'm using automated container updates, co I cannot pinpoint the server version unfortunately.
I completely wiped and reinstalled Android app.
Same situation here. Additionally I tried deactivating 2FA, but that didn't help either. Syncing with my wifes account on the same phone works.
Yeah deactivating 2FA doesn't fix the issue for me either. I'm confused on what you mean by syncing with my wife's account on the same phone works?
I logged out my account and let my wife log in to hers with my phone. Syncing worked normally with her log in. So, at least for me, it's just my account that doesn't work. I might to try to duplicate my account and try with the duplicate.
Well that's interesting. That could also possibly mean that even removing the app and re-installing seems to leave some remnant of the account on the phone. I would lean towards that assumption since everything else works except the Android app and the iphone app even though it's not as bad as the Android app it still has issues.
I think you wont find anything on bitwarden_rs since it seems "ok" from it side, but the app itself it not able to cope with one or multipple cipher maybe. I think the error would be shown more on the app itself; have you tried to the the logcat on the android app while it happen? Maybe there is a cipher it does not like for some reason.
Also for info, did you use the "clone" feature without having this commit maybe? https://github.com/dani-garcia/bitwarden_rs/commit/2ee07ea1d8a7e42ca6532f461f2aeeec4db629be If yes, probably the cloned cipher is foobar and wont sync
I do not know at all how sync actually work, so this is all speculation, but still I think the logcat could be more helpful there then the bitwarden_rs logs.
Why would the app all of a sudden after the latest update of bitwarden_rs not be able to cope with a cipher? The cipher's wouldn't change since bitwarden is served from a nginx reverse proxy as it always has been. I use watchtower to update the bitwarden_rs container so wouldn't this commit be there when watchtower cloned the latest update?
I'm just trying to wrap my head around this and what you are saying doesn't make a lot of sense to me. I'm not saying you are wrong I just don't understand it?
I don't even know where to look with logcat. I downloaded catlog but I have no idea what to do with it. I didn't know I had to turn into an Android developer to find a problem with bitwarden. This is ridiculous. This is not an app problem, this is a bitwarden problem and I would really appreciate some answers from the developer. I don't think it's too much to ask.
This is not an app problem. I know. But its the app that cannot sync.. not bitwarden_rs that cannot send the data back. There is maybe something in what the app receives from bitwarden_rs, that the android app does not like, but what, only the app would know, not the server necessarily.
My point was that maybe you added a single cipher during a period where there was a bug server side, now fixed, but that still prevents the sync. Maybe that's not what happen, I do not know, but reading other comments where using an other account work, and not the other, seems to point to a faulty cipher.
logcat can be taken with adb, and is included in minimal adb & fastboot.
Please keep in mind, I am just trying to help here. I can stop I dont mind. But I am still guessing that since the app refuses to sync, it would tell more on why. There are 3 threads on the same exact problem, and there is no traction on any. I figured I could try to get more info..
I know you are trying to help and I appreciate it. I'm just annoyed that there is no "traction" as you said. So, now I keep going back on releases until I find one that works.
I guess, if your db got "faulty", no release will work. But this is a good test, and I understand your frustration. But personally, I am using latest mobile app, android and latest bitwarden_rs, and have zero problem, so its surely not affecting everybody, so why, I would guess on something screwed up in the db. I never opened the db to check really, because for me it work, but I could check how its made. Maybe there's could be a clue on what could be unreadable by the app, or something like this. For info I am looking at this bug in particular https://github.com/dani-garcia/bitwarden_rs/issues/921. Maybe you could try a export and see if you have null data, if yes maybe that cipher would need to be deleted. In that case, it broke the android app sync.
Yeah I'm not having any luck. I went back to 1.11.0 with same results and I know for a fact I wasn't that far behind. So should I export my data, delete my account, re-create and re-import?
I exported my vault to json and I have data, if that's what you meant.
I would not go that far to be honest, and if you do so, I am afraid you will reimport the same problematic data. I would do a json export from the vault and check if there's any "null" for data, or any other suspicious "null" , and then maybe getting rid of that single (or multiple, few) cipher would work. Not sure how to actually achieve that, if the we vault permits it that might be good enough
I have 3168 "null" fields in the json export. Am I to understand that I need to remove "null" from all of them?
Here's an example:
"id": "7f4ac609-0a41-4fd8-ac5b-b1ab8c72110f",
"organizationId": null,
"folderId": null,
"type": 1,
"name": " Somename",
"notes": null,
"favorite": false,
"login": {
"username": "usrname",
"password": "redacted",
"totp": null
},
"collectionIds": null
},
No, not at all, the one you pasted for example, looks fine, I would check if any have, null username/passwd, or name. That would be out of place. Null can be legit that's the thing. But its also impossible in other cases.
Also having the response from api/sync would definitely help, to see null "data" from the json
Fixed it! 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.
Thanks a lot for the help!
Did the same, removed some empty username / password entries, it's syncing now. Thank you.
In Android bitwarden app the vault shows as empty. When I try to sync it throws a "Syncing failed" error.
this just started after upgrading to Bitwarden_RS Version 1.14.1-93346bc0. Version prior to that worked.
Container logs don't show an error only this entry during sync:
[2020-03-26 12:50:30][response][INFO] GET /api/sync? (sync) => 200 OK
Web browser works fine. Windows app works fine, Chrome extension works fine.
Additionally, I just found out that in the iPhone app you have to logout/login and then it would sync where normally it would auto sync. Force sync does seem to work in the iPhone app.
Here are some trace logs:
Hope this info helps.
I would appreciate some help.