> For the complete documentation index, see [llms.txt](https://docs.novawallet.io/nova-wallet-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novawallet.io/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault-legacy/troubleshooting.md).

# Troubleshooting

<details>

<summary>Error: Please Add The Network You Want To Transact In </summary>

<img src="https://2862319636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1YRoR7fazGxiQsx9pH6m%2Fuploads%2FRyLRCSOE8rPSovfB2rdK%2FError%20-%20Add%20the%20Network%20-%20to%20Transact%20in.png?alt=media&amp;token=2e85ca9b-118c-49b3-a940-8811f547f21e" alt="" data-size="original">

You will receive this error when you have not added the chain specs for the network on which you are trying to transact. Follow [these instructions](/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault-legacy/update-chain-metadata-in-polkadot-vault.md) on how to add chain specs and metadata.

</details>

<details>

<summary>Error: Please Download Network Metadata</summary>

![](https://2862319636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1YRoR7fazGxiQsx9pH6m%2Fuploads%2F6spNYUJThmQ9vxiTyvug%2FError%20-%20Download%20Network%20Metadata.png?alt=media\&token=34f46390-2ac0-439b-825e-5dd0c2e751bb)

You will receive this error when you have not added/updated the metadata for a network to which you have previously added the chain spec. This issue is usually caused due to a recent runtime upgrade on the chain you are trying to transact on.

Follow[ these instructions](/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault-legacy/update-chain-metadata-in-polkadot-vault.md) on how to update a chain's metadata.

</details>

<details>

<summary>Error: Transaction author public key not found.</summary>

<img src="https://2862319636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1YRoR7fazGxiQsx9pH6m%2Fuploads%2FocoAgdtMW3zCjJ9nQJDv%2FError%20-%20Author%20Public%20Key%20Not%20Found.png?alt=media&amp;token=9f938d0b-c336-4510-a1c0-cf2cc4b9cd97" alt="" data-size="original">

This error occurs when your Polkadot Vault doesn’t have a public key associated with the network you’re operating with.

To solve this:

1. `Open` the **Key Set** you’re operating with on the <mark style="background-color:purple;">Polkadot Vault Device</mark>.
2. `Tap` to **+** at the top right corner of the screen.
3. `Select` the **net**work you’re operating with.
4. Enter the **derivation path** or make it empty if you don’t use derivation.
5. `Tap` **Done**.
6. `Confirm` that you’ve written down the derivation path and **continue.**

</details>

## Still have any issues with Polkadot Vault?

Please let us know by contacting us via email at <support@novawallet.io> and sending the following information:

1. Issue description — what happened?
2. Polkadot Vault information: device platform (iOS/Android), app version and the issue on <mark style="background-color:purple;">Polkadot Vault Device</mark> (if any)
3. Nova Wallet information: device platform (iOS/Android), app version and the issue on <mark style="background-color:blue;">Nova Wallet Device</mark> (if any)

{% hint style="danger" %}

#### Never share your mnemonic passphrase (12 words) and/or other representation of your private keys! Admins/team members will never request it from you. Store your mnemonic passphrase/keys and any backups securely and privately.

{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.novawallet.io/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault-legacy/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.