> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/integrations/deep-links/troubleshooting-deep-links.md).

# Troubleshooting Deep Links

Troubleshooting deep links is essential for ensuring a seamless user experience. Follow these tips to identify and address issues:

1. **Verify Bravo Deep Links Settings**
   * Verify that all fields in the Bravo Deep Links settings are properly filled.
   * Ensure all necessary files have been uploaded.

### **iOS-Specific Considerations**

1. **Android Dynalink Project Settings** 
   * Make sure that your Dynalink setup has your:
     * **Package identifier** – you used to build your app.
     * **SHA-256 certificate fingerprint** – available from the Bravo publishing page.
2. **iOS Testing**
   * To test iOS deep links, use Apple's Notes app. Paste the link and tap on it to trigger the deep link, opening the app instead of the browser.
3. **Browser Behavior Check**
   * If issues persist, check the browser:
     * Look for a banner at the top prompting the user to choose to open the app instead.
     * iOS remembers the last preference and if the first time due to an error the link was opened in the browser, it will open the browser.

Related guides:

{% content-ref url="/pages/9Q6N7NwB3sHH29dLvv42" %}
[Deep Links](/integrations/deep-links.md)
{% endcontent-ref %}

{% content-ref url="/pages/o41J5bhRIjVNh86hS6Rg" %}
[Deep Links for Bravo Vision](/integrations/deep-links/deep-links-for-bravo-vision.md)
{% endcontent-ref %}

{% content-ref url="/pages/kLA13D1UPPs8dZ2qsZAJ" %}
[Deep Links for published apps](/integrations/deep-links/deep-links-for-published-apps.md)
{% endcontent-ref %}


---

# 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.bravostudio.app/integrations/deep-links/troubleshooting-deep-links.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.