> For the complete documentation index, see [llms.txt](https://ftcoders.first-tech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ftcoders.first-tech.com/first-tech-ttp-sdk-pt/area-do-desenvolvedor/codelab-implementacao-sdk-ttp/baixando-as-dependencias.md).

# Baixando as dependências

{% stepper %}
{% step %}
Agora, vamos definir nossas dependências e as versões delas. Abra o arquivo libs.versions.toml, que está na pasta gradle.
\
Definiremos o número das versões. As dependências serão separadas em três versões diferentes (dev, hml e prod) na seção \[versions].

 Ex: `taponphoneSdkV2DEV = "1.0.23"` 

Em seguida, defina a dependência na seção \[libraries].

`= "com.first-tech:taponphone-sdk-v2-hml", version.ref = "taponphoneSdkV2DEV" }`

{% endstep %}

{% step %}
Com todas as alterações concluídas, o arquivo libs.versions.toml ficará da seguinte maneira:

<figure><img src="https://556217668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0woQ0gWPzU3Qf5sP0Hxl%2Fuploads%2Fp49QNb4AJ2XotkuPLPzb%2Fimage.png?alt=media&amp;token=b6d48c41-a525-40d4-b932-dd0dfad34f10" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
&#x20;Agora vamos consumir a dependência do SDK (TTP) no arquivo build.gradle.kts do módulo do aplicativo (app). Para isso, adicione o trecho de código abaixo no bloco dependencies. Adicionaremos cada tipo de dependência separadamente: dev, hml e prod.

`"hmlImplementation"(libs.taponphone.sdk.v2.homol)`
\
`"releaseImplementation"(libs.taponphone.sdk.v2.release)`&#x20;

<figure><img src="https://556217668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0woQ0gWPzU3Qf5sP0Hxl%2Fuploads%2FdgXA5D40I35tdjBRxwSQ%2Fimage.png?alt=media&amp;token=c4abc482-ac8c-47c7-b960-c1f22c451772" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}
O arquivo build.gradle.kts ficará da seguinte maneira.

<figure><img src="https://556217668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0woQ0gWPzU3Qf5sP0Hxl%2Fuploads%2FEywoQ7XTVWvo28f8bFBM%2Fimage.png?alt=media&amp;token=8f333293-55a9-479b-b84b-39d8f98390d2" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Dentro do tópico "buildTypes", adicionaremos o seguinte trecho de código abaixo. Para que a dependencia seja baixada de acordo com nosso tipode build.

```
release {
    resValue("string", "app_name", "taponphone-mobileapp-mpp-native")
    isMinifyEnabled = false
    proguardFiles(getDefaultProguardFile("proguard-android-optimize.txt"), "proguard-rules.pro")
​
}
create("hml") {
    resValue("string", "app_name", "[HML] taponphone-mobileapp-mpp-native")
    applicationIdSuffix = ".hml"
    signingConfig = signingConfigs.getByName("debug")
}
```

{% endstep %}

{% step %}
Nosso arquivo build.gradle.kts,ficara com a seguinte maneira.Após adicionar o trecho de código, clique em Sync Now para realizar a sincronização e baixar a dependência do SDK (TTP).

<figure><img src="https://556217668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0woQ0gWPzU3Qf5sP0Hxl%2Fuploads%2Fyu8SMYyiUFNDB6mSuxgq%2Fimage.png?alt=media&amp;token=aa88bcb1-22e4-4c7c-86fa-67d493fbde26" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}
Depois disso, em External Libraries, veja que a dependência do SDK (TTP) foi baixada com sucesso. Agora, ela está disponível para uso.

<figure><img src="https://556217668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0woQ0gWPzU3Qf5sP0Hxl%2Fuploads%2FMqBAppQQwzhlK2AaEdo3%2Fimage.png?alt=media&amp;token=eb1ec1f7-8d40-4d50-9abc-0d871772ad6a" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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://ftcoders.first-tech.com/first-tech-ttp-sdk-pt/area-do-desenvolvedor/codelab-implementacao-sdk-ttp/baixando-as-dependencias.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.