play-billing-library-version-upgrade

Upgrade Android projects to the latest Google Play Billing Library.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill play-billing-library-version-upgrade-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play-billing-library-version-upgrade
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/play-billing-library-version-upgrade
Command: npx skills add https://github.com/mymx2/foreman --skill play-billing-library-version-upgrade-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step migration process required to upgrade Android projects to the latest Google Play Billing Library (PBL) version, ensuring compliance with Google's latest API standards and deprecation requirements.

Core Features & Use Cases

  • Automated Migration Pathing: Automatically determines whether a direct or stepped migration is required based on your current effective PBL version.
  • Smart Verification: Uses version-specific checklists to ensure all breaking changes, such as the shift from SkuDetails to ProductDetails, are correctly addressed.
  • Use Case: Use this skill when your project is stuck on an outdated billing library (e.g., v4) and you need to safely upgrade to the latest version (e.g., v9) while maintaining subscription and one-time purchase functionality.

Quick Start

Use the play billing library version upgrade skill to analyze my current project and perform a full migration to the latest stable version.

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 my Android project to the latest Google Play Billing Library?

To upgrade the Google Play Billing Library, this Skill automates the migration path by analyzing your current version and applying necessary API refactoring, dependency updates, and architectural transitions to reach the latest stable release.

What changed when migrating from SkuDetails to ProductDetails in Play Billing?

Migrating from SkuDetails to ProductDetails involves replacing deprecated methods with the new architectural API design, ensuring your subscription and one-time purchase functionality remains fully compliant and operational with the updated Play Billing Library.

Can I directly migrate from Play Billing Library v4 to the newest version?

Direct migration depends on your effective version, as this Skill automatically determines whether a direct or stepped migration path is required to transition older libraries like v4 safely to the latest Play Billing release.

How do I fix deprecated Google Play Billing methods in my Android app?

To fix deprecated methods, this Skill validates compliance against SDK requirements and replaces outdated API calls according to official Google documentation, ensuring all deprecated methods are correctly addressed during the Play Billing upgrade.

Why does my Google Play Billing migration require a stepped upgrade approach?

A stepped migration is required when intermediate breaking changes exist between your current version and the target release, which this Skill detects using version-specific checklists to ensure all API shifts are addressed sequentially.

Do I need to manually verify breaking changes after upgrading Play Billing?

Manual verification is not needed, as this Skill uses smart verification with version-specific checklists to confirm all breaking changes and architectural shifts are correctly addressed during the Google Play Billing Library upgrade.