Skip to main content
Most integration problems fall into a small number of categories. Work through the accordion below that matches your symptom, apply the fix, and re-test. If you’re still stuck, the Getting Help section at the bottom explains exactly what information to gather before contacting support.

​
Common Issues

Symptom: The SDK throws "App ID is required" on startup and no events reach the dashboard.The most common cause is instantiating TappdSDK with an empty or missing appId.
// ❌ Missing appId — SDK cannot initialize
const tappd = new TappdSDK({});
Checklist:
  1. Copy your App ID from the Tappd dashboard — do not type it manually.
  2. Confirm the value is not undefined or an empty string at runtime (log it to verify).
  3. Confirm you are importing the SDK correctly: import TappdSDK from '@tappd/mobile-sdk'.
Symptom: track() resolves without throwing, but no events appear in the Tappd dashboard.Work through these fixes in order:1. Enable debug mode to see SDK activity in your console:
const tappd = new TappdSDK({
  appId: 'YOUR_APP_ID',
  debug: true
});
2. Check network requests using React Native Debugger or Flipper’s Network tab. Verify that requests are being sent and returning 2xx status codes.3. Verify the API URL matches Tappd’s hosted endpoint:
const tappd = new TappdSDK({
  appId: 'YOUR_APP_ID',
  apiUrl: 'https://sdk.gotappd.com/api/v1/sdk'
});
4. Await every track() call. Dropping the await means errors are silently swallowed.
// ❌ Fire-and-forget — errors are not surfaced
tappd.track('event');
Symptom: Events tracked before identify() are not linked to the identified user profile.The merge only happens when identify() is called with at least external_id. Check both points below.Ensure you pass external_id to identify():
// Events tracked while anonymous
await tappd.track('event_1');
await tappd.track('event_2');

// Call identify with external_id — this triggers the merge
await tappd.identify({
  external_id: 'user_123',
  email: 'john@example.com'
});
Verify the anonymous ID is stable (it should be the same value across calls before identification):
const anonymousId = tappd.getAnonymousId();
console.log('Anonymous ID:', anonymousId);
If the anonymous ID changes between calls, AsyncStorage is not persisting correctly — see the AsyncStorage Issues section below.
Symptom: Sessions appear missing in the dashboard, or they expire far too quickly.Adjust sessionTimeout if sessions are expiring too soon (value is in minutes):
const tappd = new TappdSDK({
  appId: 'YOUR_APP_ID',
  sessionTimeout: 60 // 60-minute timeout
});
Verify a session is active immediately after initialization — the value should never be null:
const sessionId = tappd.getSessionId();
console.log('Session ID:', sessionId);
// Expected: sess_abc123... — not null
If getSessionId() returns null, the SDK failed to initialize. Go back to the SDK Not Initializing section.
Symptom: Only some screens are tracked, or screen views are absent even though trackScreen() is called.Use useFocusEffect instead of useEffect. With useEffect, the screen view fires only on mount. With useFocusEffect, it fires every time the screen comes into focus — which is what you want in a tab or stack navigator.
import { useFocusEffect } from '@react-navigation/native';

function MyScreen() {
  useFocusEffect(
    React.useCallback(() => {
      tappd.trackScreen('MyScreen');
    }, [])
  );
}
Also check:
  • NavigationContainer is configured at the root of your app.
  • Screen names are consistent across all calls (casing matters).
Symptom: registerPushToken() throws "User must be identified first".registerPushToken() requires an identified user. Always call identify() before you register the token.
// ✅ Correct order: identify first, then register
await tappd.identify({
  external_id: 'user_123',
  email: 'john@example.com'
});

await tappd.registerPushToken(token, 'ios');
Also verify your platform configuration:
  • iOS: Confirm APNs push certificates are uploaded to Firebase.
  • Android: Confirm google-services.json is in android/app/.
  • Both: Log the token to confirm it is not null or empty:
const token = await messaging().getToken();
console.log('FCM Token:', token);
Symptom: Each app launch generates a new anonymous ID, making it impossible to merge pre-identification events.The SDK relies on @react-native-async-storage/async-storage to persist the anonymous ID. If it is missing or misconfigured, a new ID is generated on every launch.Install the package:
npm install @react-native-async-storage/async-storage
cd ios && pod install && cd ..
Verify AsyncStorage is working correctly:
import AsyncStorage from '@react-native-async-storage/async-storage';

AsyncStorage.setItem('test', 'value').then(() => {
  AsyncStorage.getItem('test').then((value) => {
    console.log('AsyncStorage works:', value === 'value');
  });
});
If the log prints false, AsyncStorage is not functioning — check for linking errors and re-run pod install.
iOS build failures:Run pod install after adding or updating the SDK:
cd ios && pod install && cd ..
For a full clean build, remove the derived data and Pods directories first:
cd ios
rm -rf build
rm -rf Pods
pod install
cd ..
Android build failures:Clean the Gradle cache:
cd android
./gradlew clean
cd ..
Then check for version conflicts between @tappd/mobile-sdk and other packages in your package.json.
Symptom: TypeScript reports missing types or unknown properties when using the SDK.Import SDK types directly from the package — no separate @types install is needed:
import TappdSDK, { TappdConfig, CustomerAttributes } from '@tappd/mobile-sdk';

const config: TappdConfig = {
  appId: 'YOUR_APP_ID'
};

const tappd = new TappdSDK(config);
If you still see errors after the correct import, install the React Native community types:
npm install --save-dev @types/react-native

​
Debug Mode

Enable debug: true when you initialize the SDK to stream detailed logs to your React Native console. These logs are the fastest way to confirm the SDK is working as expected. 
const tappd = new TappdSDK({
  appId: 'YOUR_APP_ID',
  debug: true
});
With debug mode on, you should see messages like these: 
[Tappd SDK] Initialized with App ID: a1b2c3d4...
[Tappd SDK] New session started: sess_abc123
[Tappd SDK] Event tracked: purchase
[Tappd SDK] Customer identified: user_123
If any of these lines are absent, that step failed — use the relevant accordion above to fix it.
Disable debug: true before releasing to production to avoid leaking internal SDK logs to end users.

​
Getting Help

If you’ve worked through the relevant section above and the problem persists, contact Tappd support. To get a fast resolution, gather the following before reaching out:
1

Check your logs

Open the React Native debugger and copy any SDK-related log output.
2

Enable debug mode

Set debug: true, reproduce the issue, and capture the full log output.
3

Verify network requests

Use Flipper or Chrome DevTools Network tab to confirm whether API requests are being sent and what responses they receive.
4

Check your SDK version

Run npm list @tappd/mobile-sdk and confirm you are on the latest release.
5

Contact support with these details

  • Full error messages
  • Platform (iOS, Android, or both)
  • React Native version (npx react-native --version)
  • Tappd SDK version
  • Debug logs from steps 1–2

​
Common Error Messages

ErrorCauseFix
"App ID is required"appId is missing or empty in TappdConfigCopy your App ID from the Tappd dashboard
"User must be identified first"Called registerPushToken(), setUserAttributes(), or similar before identify()Call identify() before any method that requires an identified user
"Request failed: ..."Network failure or API errorCheck your apiUrl, verify internet connectivity, and inspect the response in Flipper
"AsyncStorage error"@react-native-async-storage/async-storage not installed or linkedInstall the package and run pod install on iOS