Skip to content

Troubleshoot Mobile SDK

Something not working as expected? Our support team is happy to help you with your installation and any troubleshooting. Just contact us.

The steps below help you narrow down the cause and show you what information to send us, so we can help you faster.

Before you dig into the details, figure out which kind of problem you’re dealing with:

  • Other surveys display as expected. Your Mobile SDK is most likely installed correctly, so the problem is probably with one specific survey. Contact our support team and send a link to the survey editor along with the ID of a user who should have seen the survey.
  • No surveys display, or user data isn’t tracked correctly. The problem is most likely with your SDK installation. See Debug Mode below.

Our Mobile SDKs come with a debug mode that helps you track down issues with your Refiner installation. When it’s active, all communication between your app and our backend server is logged.

Unlike our JavaScript SDK, the Mobile SDKs don’t show a debug panel on screen. Everything you need is in the debug logs.

You turn on debug mode when you initialize the SDK. Pass true for the debug mode parameter (for example debugMode: true on iOS, or the second argument of initialize on React Native).

Because the exact syntax depends on your platform, check the documentation and sample app in the repository for your SDK:

Debug mode is meant for development. Make sure it’s turned off in the builds you release to your users.

With debug mode active, the SDK logs every request to and response from our backend server. You’ll find these logs wherever your app’s logs normally appear while you develop, for example the Xcode console for iOS or Logcat in Android Studio.

Run through the flow that isn’t working, such as initializing the SDK, identifying a user, tracking an event or screen, and check the logs for errors or requests that never get sent.

When you reach out to our support team, send us these debug logs (copied text or a screenshot both work). They’re one of the quickest ways for us to see what’s going on.

Each Mobile SDK repository includes a sample project you can compile and run. This is a helpful way to check certain trigger behaviours in isolation, or to verify compatibility with other libraries in your stack, without changing your production app.

You’ll find the sample project in the repository for your platform:

Follow the setup instructions in the repository README, then initialize the sample app with your Refiner environment ID so you can test against your own surveys.

Sooner or later, you’ll want to test a survey again that you’ve already completed or dismissed. The easiest way to do this is to delete the data linked to your test user and start with a blank slate. You have two options:

  1. Delete your test user. Find your test user in the user list in your Refiner dashboard, for example by searching for their ID or email, then select and delete it. Deleting a user profile also deletes all survey responses linked to it.
  2. Purge all user data. Go to SETTINGS > ATTRIBUTES and click “Purge User Data”. This removes all contact data in your Refiner project, including survey responses.

After that, identify your test user again in your app so you start testing with fresh data. The “Reset User” method described in Identify user can help you sign out the current user first.