Troubleshooting: Mobile SDK
SDK initialization fails
| Check | Solution |
|---|---|
| Source ID correct? | Verify the Source ID matches your Told dashboard |
| Bundle ID matches? | The app's bundle/package ID must match the source configuration |
| SDK version compatible? | Check for dependency version conflicts |
| Internet connection? | The SDK needs network access to fetch survey data |
Surveys don't appear
- Call
Told.debugWidget()to check Logcat (Android) or console logs (iOS) - Verify the survey is activated in the Told dashboard
- Check trigger conditions — screen name must match exactly
- For Android: verify
registerNavControllerorregisterActivityCallbackis called - For iOS: verify
activateAutomaticScreenTracking()is called, or usetrackChangePage()
Screen tracking not working
Android:
- If using Jetpack Navigation, use
registerNavController(navController) - If using activity-based navigation, use
registerActivityCallback() - The screen name sent is the fully qualified destination name (e.g.,
com.myapp.HomeScreen)
iOS:
activateAutomaticScreenTracking()uses UIKit method swizzling — pure SwiftUI navigation without UIKit backing may not be detected- Use
Told.trackChangePage("ScreenName")for manual tracking
App crashes after SDK integration
- Check the crash logs for Told-related stack traces
- Ensure
Told.init()is called inApplication.onCreate()(Android) orAppDelegate(iOS) - Verify you're using a compatible SDK version for your platform target