Installation issues
hspindel opened this issue · 7 comments
I can't get this to install.
First problem was that the scripts seems to assume that AutoHotKey is installed on C:. I had it on D:. Uninstalled and reinstalled to C: and made progress.
Then the build.ahk script reports an error as shown in the attached JPG. (I couldn't copy and paste from the dialog box.) I tried moving the installation files to C: but it didn't help.
I would really like to use this utility!
Hello @hspindel, thanks for the interest in the app.
I would really like to use this utility!
If you use the precompiled binaries, you don't need to change the installation path of AutoHotkey in order to manually build.
The image shows that build script can't find the compiler in the default path, also shows the path to be %ProgramFilesX86% which is for SysWOW64 (32bit apps running under x64). AutoHotkey by default installs in %ProgramFiles%, that's why the error.
You either are removing the compiler after the installation, or running the build script with the 32bit version of AHK from a SySWOW64 parent process that inherits the wrong path to the build script.
I cloned the repo and managed to replicate the latter:
The solution for the first issue would be to not remove the compiler, the solution for the second would be to use the x64 version of AHK:
- Press Win+r.
- Type
cmd, and press Ctrl+Shift+Enter.- Accept the UAC prompt.
- Call the build script with AHK's x64 binary:
If you notice, after the repo was cloned, I manually created a directory. That is a bug I just find, however I'm not fixing it as I'm a few days away of pushing a big update that will take care of that.
Thanks for your report, as the new build script also had the same issue (even if it was completely rewritten). Also, I'll make sure the build script doesn't run into this issue anymore.
I hadn't noticed that there were precompiled binaries available. That is the best solution for me.
Thank you!!
Glad it worked out. Again, thanks for shed light into a bug that would have released again.
I used the precompiled binary to install bitwarden-autotype. It installed okay to
c:\Program Files\Auto-type\bw-at.exe.
Made a lot of progress. One thing: I can't find bw-at.ini anywhere on my computer. Where are the settings stored? They are obviously stored somewhere because they are remembered across invocations.
I want to use this with Quicken. I created a URI match in Bitwarden. I entered my Quicken password in the password field. I tried URI-1 equal to either Quicken Premier (the main window title) or Enter Vault Password (the subsidiary Quicken popup), and tried both "starts with" and "exact". Then I tried adding two URIs, one for
"Quicken Premier" and one for "Enter Vault Password". No joy.
I had changed the settings for the auto-type hotkey to be Win/Alt+A. When I hit Win/Alt+A in Quicken it says "no auto-type match found." What am I missing? Possibly something about how to format the URIs so they are recognized?
I couldn't find a log file to help debug this.
Thank you for any further help.
Howard
Found the problem. I had to right-click the taskbar icon and click "sync" after modifying the bitwarden logins.
Yes, the app is installed in %ProgramFiles%\Auto-Type as it is a protected directory. The settings are stored per-user in the "Application Data" profile directory (%AppData%\Auto-Type) which maps to:
C:\Users\<USERNAME>\AppData\Roaming\Auto-Type
In there you'll find 2 files: data.json and settings.ini. The first one is Bitwarden's encrypted vault and the second the settings for the Auto-Type app.
If you want to edit settings via its configuration file, make sure to either have the app closed or reload it after you change anything. A better option would be to use the built-in settings UI.
As for your issue with Quicken, you only need to add a URL to an existent login entry. For example, this is are my URLs for the Bitwarden Community Forum:
As it is, it'll match in a browser and an application whose executable is Notepad3.exe.
With that in mind, you only need to add the Quicken executable and that's it.
Got it working. Thank you for all your help, and for providing a much needed add-on to Bitwarden.