> For the complete documentation index, see [llms.txt](https://docs.chartbeat.com/cbp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/qa-mobile-sdk-integration/troubleshooting.md).

# Troubleshooting

### iOS SDK

| Symptom                                             | Likely cause                                                       | Fix                                                                                                                         |
| --------------------------------------------------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| No data on dashboard                                | Tracker never started, wrong account ID, or trackView never called | Enable debugMode = YES; verify setupTrackerWithAccountId:domain: runs at launch and each view calls trackView:viewId:title: |
| Pings too frequent / infrequent (for your use case) | Default interval not tuned                                         | Call setInterval: (seconds) before next trackView                                                                           |
| CocoaPods: unable to find spec "Chartbeat"          | CocoaPods cache stale                                              | pod repo update then pod install                                                                                            |

##

### React Native SDK

| Single warning react-native-chartbeat: Native module not available… | Running under Expo Go, or native module not autolinked            | Use an Expo development build / bare RN / EAS Build; for bare RN, run pod install (iOS) and clean-rebuild Android                                                                                   |
| ------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Gradle error: Could not find com.github.chartbeat:android\_sdk      | App-level Gradle overrides repositories and drops JitPack         | Add maven { url '<[https://jitpack.io'>](https://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/qa-mobile-sdk-integration/https:/jitpack.io'>) } to root android/build.gradle (or settings.gradle) |
| iOS build error: No such module 'Chartbeat'                         | Pod not installed after package install                           | cd ios && pod install                                                                                                                                                                               |
| No data in Chartbeat dashboard                                      | setupTracker not called before trackView, or account/domain wrong | Verify setupTracker('\<accountId>', '\<domain>') runs at app start, and enable setDebugMode(true) to confirm pings are firing                                                                       |


---

# 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://docs.chartbeat.com/cbp/tracking/mobile-app-sdks/qa-mobile-sdk-integration/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.