Hi, I'm trying to add new functional testing using StoreKitTest.
I would like to implement a functional testing end-to-end. Retrieving a product, then buying it, sending the receipt to the server to validate it and giving the access.
And then adding simple purchase test, upgrade, downgrade...
I was very very excited when I discovered StoreKitTest, but I'm facing to an error when the server is trying to validate it.
Do I'm doing something wrong ? Is it possible ?
I heard that the verifyReceipt endpoint can't valide receipt generated by StoreKitTest. Do someone has an idea do implement a real end-to-end functional testing ?
To be honest I'm a bit disappointed, the documentation says "implement a server-side validation", so following this recommendation the application should not do anything with this receipt excepted giving it to the server. So why adding a StoreKitTest if we can't send it to the server ?
I think that most companies are using the server as source of truth because the validation is there so, for example, this method is a bit weird IMO refundTransaction(identifier:). 🙂
I would like to implement a functional testing end-to-end. Retrieving a product, then buying it, sending the receipt to the server to validate it and giving the access.
And then adding simple purchase test, upgrade, downgrade...
I was very very excited when I discovered StoreKitTest, but I'm facing to an error when the server is trying to validate it.
Do I'm doing something wrong ? Is it possible ?
I heard that the verifyReceipt endpoint can't valide receipt generated by StoreKitTest. Do someone has an idea do implement a real end-to-end functional testing ?
To be honest I'm a bit disappointed, the documentation says "implement a server-side validation", so following this recommendation the application should not do anything with this receipt excepted giving it to the server. So why adding a StoreKitTest if we can't send it to the server ?
I think that most companies are using the server as source of truth because the validation is there so, for example, this method is a bit weird IMO refundTransaction(identifier:). 🙂
