Hybrid iOS apps: a web module's StoreKit 1 plugin can finish native StoreKit 2 transactions
In a native app that still hosts a Capacitor/Cordova web module, cordova-plugin-purchase (StoreKit 1) registers an SKPaymentQueue observer whenever the web app runs store.initialize, which many bundles do in their signed-in boot path, not only on the paywall. StoreKit 1 and 2 share one transaction queue, so a transaction the native StoreKit 2 code deliberately left unfinished (waiting for server confirmation) can reach the plugin, which posts its receipt to whatever legacy endpoint the web app uses and then finishes it (v13 finishes after verify(), which passes without a validator). Before shipping native StoreKit 2, make the module purchase-inert: unlink the plugin or replace window.CdvPurchase before the bundle boots, and close the module's paywall routes. Note the Cordova JS shim listed in public/cordova_plugins.js defines CdvPurchase even when the native plugin is unlinked. Found by reading code; confirm on a sandbox device.