I'm encountering the same issue in production with a StoreKit1-based project. After some investigation, it appears that finishTransaction(_:) removes the transaction only temporarily. The same transaction later reappears with the same product identifier, which then prevents the user from purchasing the consumable product again. Has anyone found a reliable workaround to avoid or mitigate this behavior?

I'm encountering the same issue in production with a StoreKit1-based project. After some investigation, it appears that finishTransaction(_:) removes the transaction only temporarily. The same transaction later reappears with the same product identifier, which then prevents the user from purchasing the consumable product again. Has anyone found a reliable workaround to avoid or mitigate this behavior?

Hello I'm encountering the same issue in production with a StoreKit1-based project. After some investigation, it appears that finishTransaction(_:) on iOS 26 Beta removes the transaction only temporarily. The same transaction later reappears with the same product identifier, which then prevents the user from purchasing the consumable product again. Has anyone found a reliable workaround to avoid or mitigate this behavior?