Skip to main content

Android Integration Checklist

The following is a checklist of integration tests that need to be completed to verify the integration is working as intended, as applicable:

  1. Update the Fairmatic SDK keys on the new build.
  2. Verify if the SDK is initialized at application startup (if the user is already logged in).
  3. Verify if the SDK is initialized at user login and signup.
  4. Verify if you received the success callback from SDK initialization.
  5. Ensure that SDK initialization failures are handled correctly — a simple setup retry logic should be added and an error should be displayed to the user in case the setup never succeeds, even after retries.
  6. Verify that SDK teardown is not called from onDestroy or similar lifecycle methods of an Activity of the application. Calling teardown in the lifecycle methods of an activity will cause Fairmatic SDK to go dormant if someone opens or closes the app temporarily. Fairmatic SDK should be explicitly turned off only due to business logic and not system-triggered events.
  7. Verify that the app is subscribed to the BOOT_COMPLETED intent and restarting the phone automatically triggers Fairmatic setup and any expected Fairmatic callbacks. This can be quickly verified by adding some logs in callbacks.
  8. Verify that the app is subscribed to the MY_PACKAGE_REPLACED intent. The intent is needed in case the app is upgraded and is no longer running. Subscribe to the MY_PACKAGE_REPLACED intent and start your app automatically which should trigger re-initialization of the Fairmatic SDK.
  9. Ensure that Fairmatic Error Codes during Fairmatic SDK operations are handled properly.
  10. Check for Setting Errors and Warnings.