# Testing

### Reset device

During implementation, installing different profiles on one device can be necessary. As the default behavior of the SDK is to offer the same profile on a device for reinstallation, the test device needs to be reset to issue a new profile.

With the first call of the "load" function of the Gigastore SDK, a token is stored in the **SharedPreferences** of your app to identify this device. To reset this device (and receive a new profile) you need to reset the **SharedPreferences** of your app. Please refer to the Android developer documentation on how to reset the **SharedPreferences.**

### Installing returns Error 2600

If you experience error 2600 on your Android device during [Install eSIM](/android-sdk/install-profile.md), it means the operating system does not allow direct installation. In this case, please check:

* the device is not SIM-locked
* your app is signed
* the SHA1 of the certificate used for signing is the same that was provided to Gigastore

### Installing returns "The device could not be verified"

If you experience this error on your Android device during [Install eSIM](/android-sdk/install-profile.md), it means the Gigastore server does not allow direct installation for this device. In this case, please check based on the error message:

* **"Remote Verification failed":** Your activation webhook failed. Please make sure your server returns status code 200 and "SUCCESS"
* **Device ID mismatch:** Your device was registered for another SDK key. Please make sure to [reset your device](#reset-device) after changing the SDK key.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.giga.store/android-sdk/testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.