Skip to main content
Full option table and API key setup: Installation.

Log Levels

Auto-Tracking Options

Custom API Hosts

Set both hosts when proxying SDK traffic through your domain.

Push click behavior (Android)

Also documented under Deep Links.

Troubleshooting

Basic steps

  1. Confirm Requirements (React Native 0.60+, iOS 13+, Android API 21+).
  2. Use the documented package version: zixflow-reactnative@^1.1.3.
  3. Enable debug logging while reproducing the issue.
  4. Follow the Quick Start order (install → platforms → initialize → identify → push).

Enable debug logging

Capture iOS / Android logs with your usual React Native tooling (npx react-native log-ios, log-android, Xcode, Logcat).
Turn debug logging off in production (Error or None).

SDK not sending data

  • Verify apiKey from Installation.
  • Call Zixflow.initialize once, early in the root component.
  • Call Zixflow.identify before expecting person-targeted campaigns.
  • Check network / proxy (apiHost / cdnHost) if you override hosts.

iOS push not received

  1. Push Notifications + Background Modes (Remote notifications) enabled in Xcode.
  2. Host app Podfile includes zixflow-reactnative/apn or /fcm.
  3. MessagingPushAPN / MessagingPushFCM initialized in AppDelegate (JS init alone is not enough on iOS).
  4. User identified and permission granted.
  5. Test on a physical device with valid APNs credentials in the Zixflow dashboard.

Android push not received

  1. Client google-services.json under android/app/.
  2. Google Services plugin applied; FCM credentials in the Zixflow dashboard.
  3. POST_NOTIFICATIONS granted on Android 13+.
  4. Package name matches the Firebase Android app.

Rich push / delivery metrics flaky on iOS

  1. Notification Service Extension target present with zixflow-reactnative-richpush/*.
  2. NSE deployment target matches the host app.
  3. Configure App Groups so undelivered metrics can recover on next launch.
  4. Image URL reachable over HTTPS.
See Deep Links. If iOS opens a browser instead of the app, check URL schemes / universal links. For killed-state taps, ensure linking is wired through AppDelegate / RCTLinkingManager.

Multiple push libraries

If another FCM / notifications package eats payloads, use Multiple Push Providers (onMessageReceived / onBackgroundMessageReceived). After adding an NSE, clean pods and rebuild:
Confirm Podfile entries use zixflow-reactnative / zixflow-reactnative-richpush (not outdated package names).

What to include when asking for help

  • SDK version (1.1.3), RN / iOS / Android versions, device model
  • Unfiltered debug logs covering init, identify, and the failing step
  • For push: live campaign payload (not only a local test), app state (foreground / background / killed)
Related: Push Notifications, Push Notification Tracking, Example Applications.