.gpg-id issues

[dactylroot]

I'm trying APS-freeRelease-2.0.0-SNAPSHOT.apk on a Pixel 7.

When I try to decrypt a password, I get the message "Found .gpg id, but it contains an invalid key ID, fingerprint or user ID".
I never entered or was prompted for a key ID or secret phrase for my GPG key.

Am I missing an option or setup step?

I also don't see how to remove a GPG key after it has been added.

[msfjarvis]

The key ID is read off the repository's .gpg-id file same as the pass CLI. You can edit the file from your computer and ensure it's not using a short key ID; i.e.: 3355E9B9 is invalid but 0xB7843F823355E9B9 is accepted. You can also use the FirstName LastName <email@domain.tld> notation if you prefer that instead.

Re: deleting keys, there is a PGP key management UI that can be found at Settings > PGP settings > Key manager, the keys will be listed here and will have a delete button as well.

[dactylroot]

my CLI is happy and works fine, but I'm not sure what may be my issue with my .gpg-id file. I re-ran pass init gpg-id ... on CLI so I expect it to use the proper format. This produces two lines, first being "gpg-id" and second line being my gpg-id itself.
I tried using the long key, full fingerprint, and then also using my First Last <email> format, and they all return this message "Found .gpg id, but it contains an invalid key ID, fingerprint or user ID".

[msfjarvis]

The first line being gpg-id is what's tripping it up. I've never seen this pattern anywhere but if the pass CLI is fine with it I am not opposed to making the app follow suit. I've made the change in commit e7982f1, you'll be able to test that in a few minutes with the latest snapshot.

[dactylroot]

That snapshot seems good and it identifies the key successfully from the .gpg-id file now.

Unfortunately, I now get "wrong password" when attempting to decrypt. I can confirm the password on desktop CLI with gpg --export-secret-keys -a <KEYID> gives me they same key after taking the password.

I have "Encrypt in ASCII armor mode" and "Enable passphrase caching" disabled, but I also tried with each enabled.

Is there something else I can try?

[msfjarvis]

Incorrect password shouldn't be tripped incorrectly but I'll have to check the code path again when it's not 2AM to verify that. I'll ping here once I've done my investigation.

[dactylroot]

I think the problem was again on my end. Unrelated misuse of pass on my CLI and snapshot build works great on my phone now!

Thank you for all your help.