[BUG]Can not create passwords

[Schueni1]

When I try to create a new password I get the following error message
Error from OpenKeyChain : Attempt to get length of null array

Steps to reproduce the behavior:

1. Install App Version 1.10.0
2. Try to create a new password

I'm also not able to select a gpg key from OpenKeyChain anymore.
The option in the settings menu is missing.
In case it is relevant. I'm using a Curve25519 gpg key to encrypt my passwords.

• Device: OnePlus 7T Pro
• OS: Android 10
• App Version 1.10.0

[msfjarvis]

Can you tell us the contents of your .gpg-id file?

[Schueni1]

I have two .gpg-id files because I encrypt the passwords in one folder with a different key.
Do you need both?

[joshcangit]

I also have this problem but I got a different error message.

Found .gpg-id, but it did not contain a key ID, fingerprint or user ID

This was after I updated and edited exist entries. No changes could be saved.

• Android version:
  10
• Device manufacturer:
  samsung
• Device model:
  SM-G973F
• App version:
  1.10.0

[msfjarvis]

I have two .gpg-id files because I encrypt the passwords in one folder with a different key.
Do you need both?

If you can provide both, it'd certainly be very helpful.

I also have this problem but I got a different error message.

Found .gpg-id, but it did not contain a key ID, fingerprint or user ID

Yours too, please :)

[joshcangit]

I couldn't access the one in the hidden repository but for the external repository, that file was empty.

Created a new external repository and the .gpg-id file is also empty.

[msfjarvis]

I couldn't access the one in the hidden repository but for the external repository, that file was empty.

Created a new external repository and the .gpg-id file is also empty.

Sigh, this is the exact problem I was hoping to not face. We don't ask users to select a GPG key during repo initialization so the .gpg-id file stays empty. The app's support for generating stores on-device is particularly kludgy and a source of pain over the years. If you use the store on a computer with a pass client I'd recommend initializing it there then copying it over to the phone as a workaround for now.

[msfjarvis]

I think the 'correct' workaround fix here would be to bring back the key selection activity and wire it into the repository creation flow to write a key into .gpg-id. For existing repositories, I think I can wire in a fallback for empty .gpg-id files. What do you think @FabianHenneke?

[Schueni1]

Content of the root .gpg-id:
85364A44A39EBE8CF50F41124F6C4940B6273A22
The special folder gpg-id:
CE85A9D522FECB4484ED11C3D4EF0667780D7BA1
Both keys are curve25519.

[fmeum]

I think the 'correct' workaround fix here would be to bring back the key selection activity and wire it into the repository creation flow to write a key into .gpg-id. For existing repositories, I think I can wire in a fallback for empty .gpg-id files. What do you think @FabianHenneke?

@msfjarvis This sounds reasonable, but could probably be combined into a single flow: Whenever the .gpg-id file is empty and a password should be encrypted, the user would be asked to select a key and that key's ID would then be stored in the file.

[msfjarvis]

I think the 'correct' workaround fix here would be to bring back the key selection activity and wire it into the repository creation flow to write a key into .gpg-id. For existing repositories, I think I can wire in a fallback for empty .gpg-id files. What do you think @FabianHenneke?

@msfjarvis This sounds reasonable, but could probably be combined into a single flow: Whenever the .gpg-id file is empty and a password should be encrypted, the user would be asked to select a key and that key's ID would then be stored in the file.

That makes sense and is easier as well, gonna do that. Can you look into why @Schueni1's keys fail?