play-billing-library-version-upgrade

Upgrade Android Google Play Billing Library integrations with version-specific migration checklists.

174|8|Updated Jan 9, 2024
One-click install
npx skills add https://github.com/klxiaoniu/QQVersionList --skill play-billing-library-version-upgrade-klxiaoniu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play-billing-library-version-upgrade
Source: https://github.com/klxiaoniu/QQVersionList/tree/main/.agents/skills/play-billing-library-version-upgrade
Command: npx skills add https://github.com/klxiaoniu/QQVersionList --skill play-billing-library-version-upgrade-klxiaoniu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the risk and effort of upgrading an Android app from legacy Google Play Billing Library (PBL) integrations to the latest stable version while avoiding breaking API changes and deprecations.

Core Features & Use Cases

  • Effective-version detection: Finds the “effective” billing version by checking what deprecated artifacts/APIs your code still uses, then chooses a correct migration baseline.
  • Direct vs stepped migration planning: Computes whether to migrate directly or in intermediate major-version steps based on the effective version delta.
  • Version-by-version execution checklist: Generates a targeted migration checklist that maps each major jump to required changes across SDK/environment alignment, connection handling, product model refactors, purchase flows, and final verification.

Quick Start

Use the play-billing-library-version-upgrade skill to upgrade your project from your current billing setup to the latest stable PBL and produce a stepwise checklist plus validation plan.

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 upgrade the Google Play Billing Library in my Android app without breaking deprecated APIs?

To upgrade the Play Billing Library safely, detect your code's effective billing version to set a migration baseline, then apply required refactors for BillingClient setup and product models before validating with sequential Gradle builds.

What is the difference between direct and stepped migration for Play Billing Library?

Direct migration jumps straight to the latest Play Billing Library version, while stepped migration increments through intermediate major versions. The choice depends on your effective version delta to prevent breaking API changes during the upgrade.

How do I refactor SkuDetails to ProductDetails when migrating Play Billing Library?

Refactoring SkuDetails to ProductDetails during Play Billing Library migration requires updating your product model queries and subscription upgrade flows to use the new ProductDetails API for handling purchases and subscriptions.

How do I handle pending purchases and connection lifecycle changes in the latest Play Billing Library?

Handling pending purchases and connection lifecycle changes in the latest Play Billing Library requires updating your BillingClient connection state management and purchase flow logic to comply with the new version's connection lifecycle requirements.

Can I validate my Play Billing Library migration using Gradle builds?

You can validate your Play Billing Library migration by running sequential Gradle builds and applying a version-specific checklist to verify that deprecated artifacts and APIs are fully removed from your Android project.