> For the complete documentation index, see [llms.txt](https://onestore-dev.gitbook.io/dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onestore-dev.gitbook.io/dev/cht/help/faq/apps/developer-verification.md).

# Android Developer Verification

## How do I complete Android Developer Verification if my app uses the ONE store app signing key?

Apps that use the **ONE store app signing key** may require the **final signed release APK with ONE store signing applied** to complete Android Developer Verification.

* If you need to register an existing package name or verify signing key ownership, follow the steps below.

### Steps <a href="#id-2.-steps" id="id-2.-steps"></a>

1. Start Android Developer Verification and package name registration with Google.
2. Copy the snippet provided on the verification screen.
3. Add the copied snippet to your app’s `assets/adi-registration.properties` file.
4. Build an APK/AAB that includes the file and submit it to ONE store.
5. Submit the final signed release APK with the ONE store app signing key applied to Google.
6. Complete package name and signing key verification with Google.

### Notes <a href="#id-2.-notes" id="id-2.-notes"></a>

{% hint style="warning" %}

* If your app uses the ONE store app signing key, Google may not be able to verify signing key ownership using only the APK signed directly by the developer.
* The Android Developer Verification process may change according to Google policy. Make sure to check Google’s official guidance before proceeding.
  {% endhint %}

{% embed url="<https://developer.android.com/developer-verification>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://onestore-dev.gitbook.io/dev/cht/help/faq/apps/developer-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.