> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/mobile-apps-native-sdk/mobile-sdk/troubleshooting.md).

# Troubleshooting

| Symptom                                                            | Cause and fix                                                                                                                                                                                           |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Android: `Could not find com.sirdata.cmp:android-sdk`              | `mavenCentral()` is missing from your repositories, or the version does not exist yet — check [Versions](/en/mobile-apps-native-sdk/mobile-sdk/versions.md).                                            |
| iOS build: `value of type 'X' has no member '<api>'`               | The Swift UI layer and the binary framework are at different versions. Resolve the package again, and make sure you are not mixing a local checkout with a released version.                            |
| The banner re-appears on every launch                              | Your app is deciding for itself. Use `awaitConsentDisplayDecision()` — a partial consent must re-open the banner and a capping window must suppress it, neither of which is visible from the TC string. |
| The banner never appears                                           | Read `decision.reason` (see [Logging](/en/mobile-apps-native-sdk/mobile-sdk/logging.md)). An active capping window, a complete stored consent, or GDPR not applying are all normal.                     |
| A vendor SDK reports no consent                                    | Initialization order. The CMP must be initialized — and consent collected — before the vendor SDK reads storage.                                                                                        |
| `isGdprApplies()` returns the wrong value at startup               | Before the publisher configuration lands, applicability is inferred from device geo. Await the configuration, or set `gdprDefaultApplies` to the assumption that is safe for you.                       |
| Consent from another publisher appears in the app                  | The partner / config pair changed without clearing consent. A TC string belongs to the publisher that collected it; clear stored consent when switching pairs.                                          |
| SwiftUI availability error (`only available in iOS 16.0 or newer`) | The SDK targets iOS 14. Update to the latest version rather than raising your deployment target.                                                                                                        |

## Getting help

Include, in this order: SDK version and platform, your partner ID and config ID, what `decision.reason` returned, and whether `IABTCF_CmpSdkID` is present in storage. Those four answers resolve most cases without a round trip.


---

# 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://cmp.docs.sirdata.net/en/mobile-apps-native-sdk/mobile-sdk/troubleshooting.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.