Skip to main content

SDK Testing

Testing the Kisi Mobile SDK is essential to ensure seamless access control functionality under different conditions. The following scenarios simulate common real-world situations, such as the app being killed or the phone being restarted, without reopening the app. These tests will help verify that the SDK operates reliably, providing a smooth user experience regardless of the app's state.

Unlock with killed app​

Follow these steps to test the Kisi Mobile SDK's functionality when the app has been force-closed:

  1. Turn Wi-Fi and mobile data OFF on your device.
  2. Begin the test at least 5 meters (16 feet) away from the door reader.
  3. Kill the app: From the Home Screen, swipe up from the bottom of the screen and pause in the middle of the screen. Swipe right or left to find the app that you want to close. Swipe up on the app's preview to force-close the app completely.
  4. Wait for 2 minutes to ensure the app is fully terminated in the background.
  5. Walk towards the door reader and tap your phone to the reader.
  6. Expected result: The door unlocks, confirming that the Kisi Mobile SDK can trigger access even when the app has been force-closed.

Unlock after phone restart without reopening the app​

Follow these steps to test the Kisi Mobile SDK's performance after a phone restart without reopening the app:

  1. Turn Wi-Fi and mobile data OFF on your device.
  2. Begin the test at least 5 meters (16 feet) away from the door reader.
  3. Restart your phone.
  4. Wait 2 minutes after the restart without reopening the app.
  5. Walk towards the door reader and tap your phone to the reader.
  6. Expected result: The door unlocks, demonstrating that the Kisi Mobile SDK can perform an unlock even after a phone restart without the app being reopened.