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.