Troubleshoot Android Emulator for Clover devices

United States
Latin America

You may encounter a few common issues when configuring or using a Clover device emulator. For information, see how to set up emulator in Android Studio.

Access to set up and test the emulator

Only the Owner of a merchant account can set up the emulator. If multiple members of a team need to test on emulators, do one of the following:

  • All team members log in to the emulator with the Owner account credentials.
  • Each team member creates their developer account on the Developer Dashboard and does not join as an invitee to the common developer account. When you create a developer account, a test merchant is created, and you are assigned as the Owner of that merchant. See Create a sandbox developer account.

Login failure for a production developer account for Europe

If your login attempts for a production merchant in Europe result in a Secure Sockets Layer (SSL) handshake error, reset the Clover-specific data on the emulator:

  1. Open Android Studio and verify that you have set the device target for Europe as described in Update device settings for production testing.
  2. Access the Device Manager.
  3. Search for a virtual device and click the Play icon next to it. The emulator runs the virtual device.
  4. From the emulator menu bar, click the more icon. The Extended controls window appears.
  5. Click Settings > Apps & notifications. The Apps & notifications page appears.
  6. Click App info to view a list of installed apps.
  7. Click Clover.
  8. Click Storage and then click Clear data.
  9. Click OK. The app data is cleared. You can now log in with your merchant account for Europe.

Unable to add more than one Clover device emulator

If a Clover device emulator is already running, you can add another emulator but cannot run the ./ script on the new emulator. To run the script, you need to stop the running emulator as follows:

  1. Open Android Studio and then open a project.
  2. From the main menu, click View > Tool Windows > Terminal. The Terminal window appears.
  3. Enter the adb devices command. A list of devices that are running appears.
  4. From that list, copy the name of the emulator you want to stop, such as emulator-5554.
  5. Enter the adb -s emulator-5554 emu kill command. In this command, replace emulator-5554 with the name of the running emulator.
  6. Re-run the adb devices command to verify you were able to stop the device.
  7. Launch the newly added emulator and then run the ./ script.
  8. After the app installation is completed, run the previous emulator.

Issue with Android Emulator Clover profile and Apple M1 Chip

When trying to run Clover device emulator profiles in Android Studio with a MAC M1 Apple chip, an error displays that the profile is terminated.


Device Manager error pop-up for termination of emulator process

By default, the Android Emulator runs inside Android Studio for efficient use of screen space and quick navigation between the emulator and the editor window. However, to resolve the issue, you need to run the emulator in a separate window. Some emulator features are only available when it's running in a separate window.

To run the emulator in a separate window:

  1. Open Android Studio and then open a project.

  2. From the main menu, click the Settings icon and then click Settings.

    Android Studio: Settings icon and menu option

    Android Studio: Settings icon and menu option

    The Settings page appears.

  3. From the left navigation menu, click Tools > Emulator.

  4. Clear the Launch in the Running Devices tool window checkbox.


Android Studio: Settings page

  1. Click Apply and then click OK. The next time you run a virtual device in the Android Emulator, it displays in a separate window.

For more information on general issues, see Troubleshoot known issues with Android Emulator.