> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/tracking/tracking-links/create-and-manage-links/fix-ios-14-mobile-tracking-links.md).

# Corregir enlaces de seguimiento móvil de iOS 14

Es posible que los usuarios de tu aplicación móvil tengan problemas para abrir enlaces de seguimiento si han actualizado su dispositivo Apple móvil a iOS 14. Cuando alguien selecciona un recurso en tu aplicación móvil, puede ver este mensaje de error:

{% hint style="warning" %}
**Importante:** Necesitas tener instalado un navegador web para usar esta función.
{% endhint %}

Este problema se produce cuando los usuarios:

* Tienen Google Chrome configurado como navegador web predeterminado en iOS.
* La API OpenUrl se invoca desde tu biblioteca .framework.

## Solución temporal: modifica info.plist

Tendrás que modificar el archivo `info.plist` de tu aplicación móvil y añadir `https` como cadena a la clave [LSApplicationQueriesSchemes](https://developer.apple.com/documentation/uikit/uiapplication/1622952-canopenurl) .

Modifica el archivo `info.plist` de modo que quede como el fragmento de código siguiente:

```programlisting
<key> 
     LSApplicationQueriesSchemes
</key> 
<array> 
     <string>https</string> 
<array>
```

Es probable que este problema se corrija en una futura versión de iOS, pero impact.com te recomienda probar tus enlaces en el escenario anterior y aplicar las actualizaciones sugeridas a tu aplicación móvil.


---

# 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://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/tracking/tracking-links/create-and-manage-links/fix-ios-14-mobile-tracking-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.
