Comment 2 for bug 1468038

Upon deeper debugging, it seems there is a race somewhere, which results in occasionally, a "purchased" status being sent via the dbus signal, immediately prior to the "not purchased" status, after a refund, which results in the "purchaseCompleted" action from the payment button being called.

I see an immediate fix which can be made to unity8, so I'm moving this bug there. There may be a race in libpay/pay-service as well here, but it will require further debugging to isolate. I also seem to be unable to replicate this with free apps any more, so I suspect the changes from the completed refunds feature resolved that side of the issue.