> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/credential-wallet/truvera-mobile-wallet/mobile-wallet-developer-usage.md).

# Mobile Wallet developer usage

### Test mode toggle

By default, the Truvera Mobile Wallet will be setup in "Production" mode. This means that it will interact with assets configured using the [Truvera Workspace](https://docs.truvera.io/truvera-workspace.md) in production mode or that were created with a production API key. Most developers first interact with Truvera Workspace as part of the free trial, which defaults to "Test mode". In order for the wallet to work with assets created using Truvera Workspace in "Test mode" or with a test API key, you need to go into the Wallet, click "Settings" in the footer menu, and select "Test mode". You can then flip the toggle.

If you have problems issuing a credential from Truvera to the Mobile Wallet, this is the first thing to check.

## Accessing the logs

To access the logs in the Truvera Wallet, you need to enable developer mode:

1. Got to "Settings" and then tap on the version number a bunch of times.
2. You will then see the developer menu.
   1. If you click the "Export debug logs" option emails, your team will silently receive an email containing your logs. This can help us to troubleshoot problems. We can share the logs with you if you [contact our support team](https://docs.truvera.io/support/support-services.md#contacting-support).
   2. If you click "Log Request", then it enables an option "View debug logs". This will allow you to see any errors that the app encountered.


---

# 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.truvera.io/credential-wallet/truvera-mobile-wallet/mobile-wallet-developer-usage.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.
