thunderbird / thunderbird/thunderbird-android
Unclear Error Toast "null" when no signing key is present in Openkeychain
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Steps to reproduce
- Have a stripped down PGP-Key with only secret encryption subkey present on phone in OpenKeychain
- Compose mail to PGP recipient.
- Toggle Encryption to "Encrypt" (green lock symbol)
- Hit send button.
Actual behavior
Error Toast: "send fail: null"
similar as described in #3713
Expected behavior
Better Error Message: Signing Subkey not present. (c.f. screenshots in #2175)
Perhaps additional Information Popup on intentional "no-encrypt-only"-policy. (#1961)
Environment
K-9 Mail version: 5.600
Android version: 7.0
OpenKeychain: 5.2 (52009)
Account type (IMAP, POP3, WebDAV/Exchange): Gmail IMAP + 3rd party SMTP outgoing
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the send failure using a stripped-down PGP key with only a secret encryption subkey, the listed K-9 Mail, Android, and OpenKeychain versions, and inspect send_fail_null.txt. Trace where the send error becomes "send fail: null" and confirm that the missing signing-subkey case produces a specific message, including any intentional no-encrypt-only policy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100