> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/release-notes/es/sdk/july-2025/push-provisioning-classic.md).

# Aprovisionamiento push (clásico)

{% tabs %}
{% tab title="Android - v1.12.0" %}
**Plataformas compatibles y arquitecturas de procesador**

* Android 8.0 y posteriores.
* Arquitecturas de procesador: armeabi-v7a, arm64-v8a.

**Mejoras**

* Admite "tamaños de página de 16 KB" para cumplir con el requisito de compatibilidad de Google Play. Para que la aplicación cumpla con este requisito, es necesario actualizar la dependencia JNA a la versión 5.17 o posterior, y la versión de AGP a 8.5.1 o posterior.
* La biblioteca de terceros Google Tap and Pay que anteriormente se integró en TPC SDK ha sido ofuscada. Como resultado, los integradores ya no pueden acceder directamente a la biblioteca Tap and Pay a través de TPC SDK. Si su aplicación requiere acceso a la API de Tap and Pay, deberá incluir su propia copia de la biblioteca dentro de su implementación.
  {% endtab %}

{% tab title="iOS - v2.7.0" %}
**Plataformas compatibles y arquitecturas de procesador**

* iOS 15.0 y posteriores.
* arm64, simulador x86\_64 y simulador arm64.

**Mejoras**

* Se agregó compatibilidad para el aprovisionamiento de cobadge con esquema auxiliar.

**Correcciones de errores**

* Se corrigió el problema al determinar si un token está almacenado o no en un dispositivo local.
* Se corrigió el fallo en iOS 26 Beta durante la digitalización.
  {% endtab %}
  {% endtabs %}


---

# 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.payments.thalescloud.io/release-notes/es/sdk/july-2025/push-provisioning-classic.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.