-
Notifications
You must be signed in to change notification settings - Fork 27
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
Integration with KeePassXC keeps asking for ID #55
Comments
What is your extension's version? Does the extension's interface keep open when the integration is happening? |
Extension version is 0.6.6. The extensions interface stays open while setting the ID, but after confirming the ID, both the window of KeePassXC and the extension UI close. |
Let's debug:
|
ok...I don't know what changed, but it suddenly just works. Dev Mode has always been active. In the dev tools window there were no errors in console, but after setting the ID yet another time it suddenly worked. I did the exact same thing I did just this morning when writing the previous post - of course except the part with inspect popup. So let's see if that's something permanent or if the problem reappears. |
I can confirm now that it "fixes" the problem reliably if when it keeps asking for an ID to simply use the "inspect" item on it. Then for some reason the popup seems to stay open for long enough to actually finish the connection |
I followed the instructions and created the file
~/.config/google-chrome/NativeMessagingHosts/org.keepasshelper.extension.json
with the contentand set it in the settings menu to Native Messaging. Browser integration is enabled in KeePassXC and the communication does work, but only up to the point of giving the communication key a name. Every time I enter a name for it and save it and then click on the extension icon again, it just asks again for a name for a new key. So KeePassHelper seems to request a new key every time. Why isn't it sticking?
The text was updated successfully, but these errors were encountered: