Ok, never mind – I'm not sure what was going on with my device, but it turns out you are delivered unfinished transactions on startup. The device I was using to test did an overnight OS update, so maybe there was an iOS bug that got squashed? Not sure.
In any case, if you're wondering how to best handle this… yeah, follow the documentation. Keep track of what you've done (persistently!) and call finishTransaction when everything's complete.
(Actually, just in case you're still having this same bug and you're in precisely the same situation I was in – Plugin.InAppBilling has a number of critical bugs for iOS consumables, which I've raised in issue #466 on their GitHub. Try it again with a fresh Xcode project in Swift or Objc. This didn't fix my problem, but it did allow me to figure out that the plugin was bugged when suddenly the test Xcode project started working.)
gormster_
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Time for an emergency patch, Apple!