B2 credentials somehow no longer work on new Mac install

I have now installed the GUI on a Mac (OS 10.11.6). I’m setting up the first job and have two issues.

  1. I’ve entered my B2 account ID and Application Key by copy and paste from my password master file, same as I have done on my 3 prior installs (on Windows PCs) without a problem. Yet I get, repeatedly, failed to load … authentication failure before I get to the storage password dialog. Shouldn’t these two credentials be the same on Mac vs. PC?
  2. I get pestered by repeated duplicacy wants to use your confidential information stored in “duplicacy” in your keychain popup dialogs. Two dialogs for each repeated attempt. I click Deny to dismiss each one; only then does the B2 error message in 1 above appear. It’s almost as if Keychain is involved somehow in causing my credentials to fail.

I don’t have a direct answer, but it seems both points are connected. Have you read this: Passwords, credentials and environment variables ?

This is the Duplicacy CLI version asking for the permission to read credentials stored by the GUI version. You should click Always allow or Allow, otherwise the CLI version would not be able to read any credentials and hence the ‘Failed to load…’ errors with the B2 storage.

Thanks Christoph and gchen. That was the issue.

But now I have another problem. Please tell me I’m doing something wrong, but it appears I cannot paste my storage password into its fields in the storage setup. If this is correct it is a big problem. My storage password is very long, and is an entirely random string of upper and lower case letters, numbers, and special symbols. And I have to type it character-by-character correctly, twice. I’ve spent some minutes trying to do this already, without success.

With the help of another human, I got this done, and the initial backup of the Mac is underway. But my initial plea remains: You can’t be serious about not allowing pasting into these fields. Am I right?

You can’t be serious about not allowing pasting into these fields. Am I right?

I fully agree. I seem to remember having raised that very same issue a while ago (can’t seem to find it now, though).

This is a limitation of wxWidgets. I’ll try to find a workaround.