play-billing-library-version-upgrade

Upgrade Android apps from legacy Google Play Billing Library versions to the latest stable release.

6.6k|388|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/android/skills --skill play-billing-library-version-upgrade-android
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play-billing-library-version-upgrade
Source: https://github.com/android/skills/tree/main/play/play-billing-library-version-upgrade
Command: npx skills add https://github.com/android/skills --skill play-billing-library-version-upgrade-android

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy Play Billing Library (PBL) integrations break or become unsupported as APIs evolve, forcing teams to manually untangle compile-time errors and behavioral changes during upgrades and migrations.

Core Features & Use Cases

  • Dependency and effective-version discovery: Detects the current billing library version from Gradle files and uses a fallback scan of deprecated APIs to determine an accurate “effective” baseline when builds fail.
  • Direct or stepped migration planning: Computes whether the upgrade should be direct or performed in major-version steps, then ties each step to the correct migration guides and release-note deltas.
  • Production-grade code refactoring and validation: Produces an execution plan that covers required builder configuration changes, API/model swaps (SkuDetails→ProductDetails), purchase querying updates, connection management changes, and a version-specific checklist verification flow with gradle-based build/test commands.

Quick Start

Use this skill to upgrade your Android app from any legacy Google Play Billing Library version to the latest stable version by following the generated migration checklist and validation steps.

Frequently Asked Questions about play-billing-library-version-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Android app from legacy Play Billing Library to the latest version?

Migrating SkuDetails to ProductDetails requires replacing legacy Play Billing models with the new ProductDetails API. You must update purchase querying, swap model objects, and modernize subscription flows according to the version-specific migration checklist generated by the skill.

What is the best way to handle Google Play Billing dependency alignment during an upgrade?

The best way to handle Play Billing dependency alignment is to detect the current library version from your Gradle files and compute whether a direct or stepped major-version migration is required. This ensures your dependency configuration matches the correct migration guides and release-note deltas.

Can I skip major versions when upgrading Google Play Billing Library in my app?

When your Gradle build fails after a Play Billing upgrade, you can determine your effective billing baseline by performing a fallback scan of deprecated APIs. This scan identifies the accurate legacy version baseline when standard dependency detection is unavailable.

Do I need to update connection management when upgrading the Play Billing Library?

You need to update connection management when upgrading the Play Billing Library to resolve behavioral changes and API removals. The migration process generates required builder configuration changes and validates them using version-specific checklist verification flows with Gradle-based build and test commands.