play-billing-library-version-upgrade

Refactoring SkuDetails to ProductDetails during a Play Billing Library upgrade involves migrating to offering-based subscriptions and replacing legacy subscription update parameters. The skill provides specific refactor guidance and API change mappings for these transitions.

Migrating SkuDetails to ProductDetails in Play Billing involves transitioning to offering-based subscriptions and updating subscription parameters. The skill prescribes specific refactors, release note references, and compatibility updates to handle these API changes.

Yes, you can use a stepped migration instead of a direct upgrade for the Play Billing Library. The skill assesses your effective version baseline and plans either a direct or stepped migration path to the target version depending on your project's environment alignment.

To validate your Android project after upgrading Google Play Billing Library, run the prescribed tests and complete the per-version validation checklist provided by the skill. This final validation step ensures environment alignment and confirms auto-reconnection handling works correctly.

You need to handle auto-reconnection changes in the Play Billing Library when upgrading across major versions that alter connection lifecycle APIs. The skill identifies these API changes and prescribes the necessary refactors to maintain stable billing connections.