This issue is extremely burdensome. In order to test purchases in the sandbox env I have to reset my device sometimes serveral times a day.I am finishing these transactions. I know this is the case because I've set up several brand new sandbox testers and confirmed via code inspection and debug breakpoints that my code is finishing purchase transactions correctly. So that leaves me wondering what could be possibly going wrong that's in my control to fix, or even workaround in a less burdensome manner than resetting all content and settings.I've filed FB7645732 along with details and a sysdiagnose, and am hoping that it can get some traction.

Correct.

Resetting all content and settings has allowed me to get out of this strange state. Sandbox purchases now work for me as before (with a fresh sandbox user) on the reset device.

As I've investigated further, I'm seeing something else that's curious, which I think might be related. Back in February, I found and fixed an issue where my app wasn't calling finishTransaction() appropriately. The completed sandbox payments that I see arriving on the paymentQueue have transaction dates from right around that time. This may just be a coincidence since it's the last time that I tested sandbox purchases, or it may indicate that the sandbox server is deciding to ensure that clients properly deal with all old transactions that are hanging around before acknowledging any new purchase attempts. I'd like to know if other folks who are encountering this issue have also forgotten to ensure that they're calling finishTransaction()?