Sign in and claim your SDKs

With Google Play SDK Console, you can reach developers in Play Console, Play SDK Index, and Android Studio, and obtain valuable insights about your SDKs.

• Communicate important information about your SDKs to the developers that use them. Report an SDK version as outdated or add a note if it has a known issue.
• View crash and ANR reports to fix issues in your SDKs. Receive full stack traces shared by app developers and add notes to help developers understand what caused the issue and how to prevent it. Stay on top of security vulnerabilities and issues in your SDKs that may cause apps to violate Google Play Developer Program policies.
• View and analyze aggregated metrics for your SDKs on apps distributed through Google Play. Monitor adoption trends, proportion of install base across different dimensions, and market share per app category.

Use an existing Google account or create a new Google account to sign in to SDK Console. If you are using a Google Workspace account, make sure your admin has enabled access to Google Play. You must use an individual Google account; Google Groups are not supported.

Once you sign in, you can invite other users via their Google accounts and manage individual user permissions.

Create an SDK Console account and claim your first SDK

To start using SDK Console, you’ll need to enter the Maven ID for an SDK that you own. This SDK must be eligible for SDK Console, and you’ll need to prove ownership by publishing a new version including a verification file.

1. Sign in to SDK Console.
2. Enter the Maven ID of an SDK that you own and want to claim in the SDK Console. You can add more later.

• Note: A Maven ID is the identifier app developers use to download your dependency from the Maven repository. It is composed of a Group ID and an Artifact ID separated by a colon sign (":"), for example, "com.example.foo:bar."

3. Select Check eligibility. See SDK eligibility for SDK Console for more information.
4. If your SDK is eligible, select Next and proceed to Verify ownership of your SDK.
5. Once ownership of your SDK has been verified, select Next and enter the developer details for whom you’re creating the account for:

• Public developer name: This is typically your organization name, and how your developer name will appear across Google Play.
• Email address: We’ll use this to contact you. It can be different from the email address associated with your Google Account and won’t be visible to users on Google Play.
• Phone number: We’ll use this to send you information about your account. It won’t be visible to users on Google Play.

6. Select Next, review and accept the Google Play SDK Console Terms of Service, and select Create account.
7. Finish claiming your SDK by selecting Add SDK details and adding the following information:

• Name: This is how your SDK name will appear across Google Play.
• Description: Add a short description of your SDK, explaining what it does.
• Icon: Add an icon to represent your SDK across Google Play. Icons must meet the following requirements:
  • JPG or 32-bit PNG (not transparent)
  • 512px by 512px
  • Up to 1MB
• Category: Choose the most suitable category for your SDK. You can choose more than one that applies.
• Documentation URL: Add a link to the documentation for your SDK.
• Privacy policy URL: Add a link to the privacy policy for your SDK.
• Data safety section guidance: Add a link to any Play Data safety section guidance you make available to your customers for your SDK. If you haven't yet prepared this documentation, you might consider using this Optional format for SDKs.

Claim additional SDKs

To claim additional SDKs, you’ll need to verify ownership and add details for each SDK:

1. Sign in to SDK Console and select SDKs on the left menu.
2. Click Add SDK.
3. Enter the Maven ID of an SDK that you own and want to claim in SDK Console.
   • ​​Note: A Maven ID is the identifier app developers use to download your dependency from the Maven repository. It is composed of a Group ID and an Artifact ID separated by a colon sign (":"), for example, "com.example.foo:bar." You will only have to prove ownership of the domain of the group ID ("example.com" in the previous example) once for all SDKs under that domain.
4. Select Check eligibility, and when successful, click Add. See SDK eligibility for SDK Console for more information. The SDK will appear under Finish claiming on the SDKs page.
5. Select Verify ownership. See Verify ownership of your SDK for more information.
6. Once ownership of your SDK has been verified, select Add SDK details and finish claiming it by providing details about the SDK.

• This includes choosing an SDK category, uploading an icon, and more. You can change this information later if needed.

7. Repeat steps 2-6 for each SDK you want to claim.

After you've claimed an SDK, you can see the full list of SDKs you've claimed under Claimed SDKs on the SDKs page. You can click on an SDK to see a list of its versions.

SDK eligibility for SDK Console

An SDK is eligible for Google Play SDK Console as long as it is distributed from a canonical Maven repository source that we can verify.

If you see the "This SDK can't be claimed in SDK Console" error when checking if your SDK is eligible, it means that we can’t determine the canonical Maven repository source for this SDK. Contact us to provide us with your repository URL.

If you are using a private Maven repository, contact us to provide us with the credentials.

If you are using a non-Maven distribution channel, contact us and tell us how you distribute your SDK.

Verify ownership of your SDK

You must release an updated version of the SDK with a verification file attached in order to prove your ownership of the SDK.

1. Download the verification file for your SDK by selecting Download. This verification file is unique for your SDK Console account and will be the same for all the SDKs that you verify within the account.
2. Unzip the downloaded file into the main folder of your Android SDK. This will extract a file named "verification.properties" within this path src/main/resources/META-INF/[Your_SDK_NAME].
3. Build your SDK and ensure that the verification file is included in your binary.
4. Publish this new version of your SDK to your repository. The verification file can be included in SDKs published to public Maven repositories, and it does not need to be present in future SDK releases.
5. You can leave this step and come back to it later. We'll contact you by email when we've verified ownership. The process can take up to 14 days.

It's possible that we might have chosen the wrong canonical repository for your SDK. Contact us if you need to update or correct the canonical Maven repository.