Breaking Changes & New Subscription Plan Transition APIs

Developers should be aware of several breaking changes: the packageName and token parameters are now strictly required in certain API calls, and the transitionState property within the TransitionInfo schema has become read-only. Ensure your integrations provide these required parameters and do not attempt to modify transitionState. Alongside these changes, the API gains powerful new capabilities for managing subscription plan transitions. Two new methods, purchases.subscriptionsv2.cancelplantransition and purchases.subscriptionsv2.scheduleplantransition, are now available. These allow you to programmatically cancel an in-progress plan transition or schedule a future one. Supporting schemas like PlanTransitionDetails, TransitionInfo, DefiniteTransition, and TentativeTransition have been added to facilitate these operations, providing granular control over subscription lifecycle management.