pbl-v7-to-v9-migration

Automate Android app migration from Play Billing Library 7.x to 9.x.

45|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/RevenueCat/play-billing-skills --skill pbl-v7-to-v9-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbl-v7-to-v9-migration
Source: https://github.com/RevenueCat/play-billing-skills/tree/main/google-play/pbl-v7-to-v9-migration
Command: npx skills add https://github.com/RevenueCat/play-billing-skills --skill pbl-v7-to-v9-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of migrating Android apps from Play Billing Library 7.x to 9.x, ensuring a smooth transition with minimal downtime.

Core Features & Use Cases

  • Two-Stage Migration: Provides a structured two-stage process for migration: from v7 to v8 and then to v9.
  • Detailed Renaming Map: Offers a comprehensive list of API and class renames required for migration.
  • Dependency Management: Assists in updating dependencies and SDK versions for compatibility with PBL 9.
  • Verification Flow: Includes a verification process to ensure successful migration and compatibility.

Quick Start

Run the pbl-v7-to-v9-migration skill to begin the migration process for your Android app.

Frequently Asked Questions about pbl-v7-to-v9-migration

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

FAQPage Schema
How do I migrate my Android app from Play Billing Library 7 to 9?

To migrate from Play Billing Library 7 to 9, you follow a structured two-stage process: first upgrade from v7 to v8, then from v8 to v9, applying detailed API renaming guidance and updating SDK versions.

What API renames are required for Play Billing Library 9 migration?

Play Billing Library 9 migration requires applying a comprehensive list of API and class renames provided by the migration guide, ensuring your Android app codebase maintains compatibility with the updated PBL 9 specifications.

Do I need to update SDK versions when upgrading to Play Billing Library 9?

Yes, upgrading to Play Billing Library 9 requires updating your Android SDK versions and dependencies to ensure full compatibility with the new PBL 9 specifications and a successful migration.

What is the best way to handle Play Billing Library versioning upgrades?

The best way to handle Play Billing Library versioning upgrades is using a two-stage migration plan that transitions from v7 to v8, then v8 to v9, ensuring minimal downtime and structured API renaming.

Can I migrate Android apps directly from PBL 7 to PBL 9 without an intermediate step?

Migrating Android apps from PBL 7 to PBL 9 is structured as a two-stage process involving an intermediate v8 step, which ensures proper API renaming and dependency management before reaching full v9 compatibility.

How do I verify a successful Play Billing Library 9 migration?

You verify a successful Play Billing Library 9 migration by following the included verification flow, which checks that your Android app's API renames, SDK versions, and dependencies are fully compatible with PBL 9.