```
### Ofuscación
Si tu aplicación tiene problemas de ProGuard con Samsung Pay, usa las siguientes reglas:
# Samsung Pay
-keep class com.samsung.android.sdk.** { *; }
-keep interface com.samsung.android.sdk.** { *; }
A continuación se muestran las reglas de ofuscación recomendadas por Google:
{% code overflow="wrap" %}
```
# Google Pay
# Conservar las clases e interfaces del cliente del SDK TapAndPay
-keep class com.google.android.gms.tapandpay.** { *; }
# Evitar la eliminación o el cambio de nombre de las clases SafeParcelable y sus campos CREATOR
-keep class * implements com.google.android.gms.common.internal.safeparcelable.SafeParcelable {
public static final android.os.Parcelable$Creator *;
}
# Conservar los campos creador Parcelable estándar
-keepclassmembers class * implements android.os.Parcelable {
public static final android.os.Parcelable$Creator CREATOR;
}
```
{% endcode %}
---
# 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/classic-push-provisioning/es/guia-para-desarrolladores/configuracion-del-sdk/android.md?ask=&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.
