1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
+++
title = "Troubleshooting"
date = 2026-11-05T00:00:00Z
description = "Common HardenedPass errors, what they mean and how to fix them: passphrase, keys, SSH, push rejected, detached head, autofill."
weight = 110
draft = false
+++
## Keys and passphrases
**The app asks for the passphrase again and says it is wrong.** The passphrase does not
match the private key. If you changed the key's passphrase on a computer, the app
needs the new one. If caching is on, it asks again and replaces the old value.
**`Failed to import PGP key`.** The file is not a key the app can use. Keys without an
encryption subkey are rejected, because they could not decrypt anything. Check that you
exported the **private** key, with `gpg --armor --export-secret-keys`.
**An entry will not open and no key matches.** The store is encrypted for a key that is
not imported. Compare **Store recipients** on the import screen, or the `.gpg-id` file,
with the keys in **Key manager**. A public key alone cannot decrypt: import the private
one.
**The key is on a smartcard.** GnuPG exports a stub for such a key, with no secret
material in it. The app cannot decrypt with that. It needs the real private key.
**`Found .gpg-id, but it contains an invalid key ID, fingerprint or user ID`.** The
`.gpg-id` file has something the app does not understand. Check it on a computer: one
key ID, fingerprint or address per line.
## Connecting
**`The provided repository URL is not valid`.** See the address forms in
[Connect the app]({{< relref "/hardenedpass/getting-started/connect" >}}).
**`Wrong password` or `Wrong passphrase`.** For a repository password or an SSH key's
passphrase. Many hosting services want an access token rather than the account password.
**`Selected file does not appear to be an SSH private key`.** You picked the public key,
or a file in another format. Choose the file without `.pub`.
**The sync fails after the server was reinstalled or moved.** Its host key changed. If
you are sure why, use **Clear saved host key** on the repository screen, under **Edit
Git server settings**. If you are not, treat it as an attack until you know better.
**SSH login is refused.** Check that the public key is on the server, for the right
account. **View generated public SSH key** shows it for a key made on the phone.
## Syncing
**`Push was rejected by remote, run pull before pushing again`.** The server has commits
you do not have. Use **Synchronize repository**, which pulls and then pushes.
**`Pull has failed, you're in a detached head`.** A conflict stopped the rebase.
[Sync]({{< relref "/hardenedpass/using/sync" >}}) has the steps.
**`Merge has failed, you're in a conflicting state`.** The same conflict, with **Rebase
on pull** off. The way out is the hard reset in
[Sync]({{< relref "/hardenedpass/using/sync" >}}), after saving anything you need.
**`The repository must be cloned before syncing changes`.** The store on the phone has no
remote. Set one under **Edit Git server settings** and clone it.
## Autofill
**No suggestions appear.** Check that HardenedPass is the selected autofill service in
Android's settings, and that the browser is on the list in
[Autofill]({{< relref "/hardenedpass/using/autofill" >}}).
**An app says no password manager was found.** It uses Android's password manager, not
autofill. Turn HardenedPass on under **Passwords, passkeys & accounts**, as in
[Autofill]({{< relref "/hardenedpass/using/autofill" >}}). This needs Android 14 or later
and HardenedPass 0.3.4 or later.
**Only the password gets filled.** That is the browser's support level, as with Vanadium.
**`This app is currently not supported`.** The app cannot save from there. You can still
add the entry by hand.
**Nothing happens after tapping Save.** Android 14 and later hold back background
windows, and the app has a workaround: update to the latest version.
## Still stuck?
Open an issue on the [tracker](https://github.com/danixland/HardenedPass/issues). Say
which version you run (**About** shows it) and what you did. Never paste passwords, keys
or real entry names.
A log helps a lot:
1. In **Settings**, then **Misc**, turn on **Debug logging** and restart the app.
2. Do what goes wrong.
3. Tap **Export log** in the same place and choose where to save the file. Do this soon,
and before restarting the phone: Android keeps only recent lines.
4. Turn **Debug logging** off again.
5. Read the file and remove what you do not want public, then attach it to the issue.
The file can show entry names, websites, apps and your git server. Crashes are in it
even with **Debug logging** off.
|
