> For the complete documentation index, see [llms.txt](https://doc.newsfreak.mrb-lab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.newsfreak.mrb-lab.com/additional-setup/11.-deep-app-links-setup/11.2-android-setup.md).

# 11.2 Android Setup

1. From your Cpanel, go to the **File Manager > Your Site > .well-known** folder and create a file named **assetlinks.json** and open the file and insert the following code.

```json
[
    {
        "relation": [
            "delegate_permission/common.handle_all_urls"
        ],
        "target": {
            "namespace": "android_app",
            "package_name": "com.mrblab.newsfreak",
            "sha256_cert_fingerprints": [
                "56:35:86:19:1F:37:76:31:7F:16:F5:48:0F:8A:67:D8:42:3A:98:09:A0:45:3D:18:E9:F1:40:04:CB:30:52:54",
                
                "4C:5F:7D:8F:45:F8:AF:BF:06:21:FA:76:0A:A5:FC:0B:17:38:42:7F:55:DE:B8:BA:50:85:D4:DA:DD:0B:63:C9"
            ]
        }
    }
]
```

2. Replace the package\_name value with your **Android package name**.
3. Now you need to generate two **sha256** fingerprints (Debug and Release).
4. Replace the **sha256\_cert\_fingerprints** values with your values.&#x20;
5. Save the file. Now, You can check on this site if your deep link setup working not: <https://developers.google.com/digital-asset-links/tools/generator>

<figure><img src="/files/tYBSnzU7Emo9iZlBcYNh" alt=""><figcaption></figcaption></figure>

5. From the source code, go to the **android/app/src/main/AndroidManifest.xml** file and add your site URL.

<figure><img src="/files/nfuhvq8NcCK0v40EMnz9" alt=""><figcaption></figcaption></figure>

That's it. Android configuration for deep/app links is complete.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.newsfreak.mrb-lab.com/additional-setup/11.-deep-app-links-setup/11.2-android-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
