anonymous1184/bitwarden-autotype

random error happening, can only be fixed by restarting the program

cpainchaud opened this issue · 4 comments

cpainchaud commented

The following error happens often and right now everytime I hit the Sync button I am getting this screen
image

along with log:

{
	"A_Error": {
		"Extra": "Unexpected character at position 1: 'V'",
		"File": "bw-at.exe",
		"Line": 832,
		"Message": "Failed to parse JSON (-1,0)",
		"What": "-1"
	},
	"A_Info": {
		"locked": 0,
		"logged": 1,
		"portable": 1,
		"session": 0,
		"status": "locked",
		"sync": "2023-02-10T12:36:54.575Z",
		"version": "1.1.33.10",
		"windows": "10.0.19045"
	},
	"ADVANCED": {
		"field": "auto-type",
		"NODE_EXTRA_CA_CERTS": "Present",
		"pin-length": "6",
		"reprompt-with-pin": "1",
		"server": "Present",
		"tcato-ksps": "10",
		"tcato-wait": "250",
		"update-frequency": "1"
	},
	"CREDENTIALS": {
		"api-key": "0",
		"client-id": "",
		"client-secret": "",
		"tsl": "2",
		"user": "Present"
	},
	"DATA": {
		"pin": "Present",
		"update": "1676019288",
		"version": "1.1"
	},
	"GENERAL": {
		"action": "1",
		"favicons": "0",
		"pin": "2",
		"sync": "10",
		"tcato": 1,
		"timeout": "10",
		"totp": "1",
		"updates": "1"
	},
	"GENERATOR": {
		"digits": "1",
		"exclude": "",
		"length": "39",
		"lower": "1",
		"symbols": "1",
		"upper": "1"
	},
	"HOTKEYS": {
		"default": "#!v",
		"password": "^!p",
		"totp": "^!o",
		"username": "^!u"
	},
	"SEQUENCES": {
		"default": "{ClearField}{Username}{SmartTab}{Password}{Enter}",
		"password": "{ClearField}{Password}{Enter}",
		"totp": "{TOTP}",
		"username": "{ClearField}{Username}"
	}
}
anonymous1184 commented

For some reason it reports being locked yet, you are synchronizing.

The issue in itself is that the CLI doesn't receive a JSON string, rather a string starting with the letter V.

Sorry for the late reply but, the issue still persists?

LoserForever88 commented

Can confirm it still persists. The same error occurs once the autotype vault is locked. Unlocking it afterwards doesn't solve the problem and the synchronization just keeps running. The error just keeps popping up if you dismiss it.

anonymous1184 commented

@LoserForever88 are you using a self-hosted instance too?

The letter V seems to be an indicative of VaultWarden, so the problem would be on the server side of things, given that an official instance for example doesn't preset the issue.

LoserForever88 commented

@LoserForever88 are you using a self-hosted instance too?

The letter V seems to be an indicative of VaultWarden, so the problem would be on the server side of things, given that an official instance for example doesn't preset the issue.

No, I'm using offical installation. I tried it again. Same error and the sync just couldn't pass through once the vault is manually locked.