Skip to content
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

an error occured #15

Closed
Nypheena opened this issue Oct 9, 2021 · 3 comments
Closed

an error occured #15

Nypheena opened this issue Oct 9, 2021 · 3 comments

Comments

@Nypheena
Copy link

Nypheena commented Oct 9, 2021

{ "A_Error": { "Extra": "Unexpected character at position 1: 'Y'", "File": "bw-at.exe", "Line": 833, "Message": "Failed to parse JSON (-1,0)", "What": "-1" }, "A_Info": { "locked": 0, "logged": 1, "portable": 1, "status": "unauthenticated", "sync": null, "version": "1.1.1.1", "windows": "10.0.19041" }, "ADVANCED": { "field": "auto-type", "NODE_EXTRA_CA_CERTS": "", "pin-length": "4", "reprompt-with-pin": "1", "server": "", "tcato-ksps": "10", "tcato-wait": "250", "update-frequency": "1" }, "CREDENTIALS": { "tsl": 2, "user": "Present" }, "DATA": { "pin": "", "update": "1633742864", "version": "1.0" }, "GENERAL": { "action": "0", "favicons": "0", "pin": "0", "sync": "15", "tcato": "1", "timeout": "0", "totp": "2", "updates": "1" }, "GENERATOR": { "digits": "1", "exclude": "", "length": "39", "lower": "1", "symbols": "1", "upper": "1" }, "HOTKEYS": { "default": "^!a", "password": "+^!s", "totp": "^!o", "username": "^!u" }, "SEQUENCES": { "default": "{ClearField}{Username}{SmartTab}{Password}{Enter}", "password": "{ClearField}{Password}{Enter}", "totp": "{TOTP}", "username": "{ClearField}{Username}" } }

@nefrog
Copy link

nefrog commented Oct 9, 2021

I'm also getting this same error with both the portable and stand alone version. The error seems to occur when attempting to sync with bitwarden cli.
v 1.1.1.
image

@anonymous1184
Copy link
Owner

anonymous1184 commented Oct 9, 2021

Seems to be an error because of the new bot detection on Bitwarden CLI. I'm going to report the issue but for now seems that the only workaround would be to log via API Key. However even that has a lot of issues for the moment being:

So far issues 383 and 384 are related to this and the one I'm about to report make it the 3rd.

EDIT: Here is the issue 385 (created by me), which is what's happening in this case.

@anonymous1184
Copy link
Owner

Release v1.1.2 address this by using a Personal API Key as login method. If Bitwarden Team fixes the issue, regular login will be enough without further code modifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants