Reputation: 191
We are getting HTTP 404 when trying to download the certificate for validating the receipt. I've seen two different URIs to fetch the certificate, of which the other is a redirect to the first one. Below is the supposed URI to the certificate:
Certificate with id: A656B9B1B3AA509EEA30222E6D5E7DBDA9822DCD
The address should be fine as I'm able to download another certificate with a different id mentioned here (id: b809e47cd0110a4db043b3f73e83acd917fe1336)
My guess is, that this is due to our app being a beta app at the moment and since I can find the same certificate id from the example receipt in this sample here, but haven't been able to verify it.
Edit: the in-app products are also free at the moment if that matters
Upvotes: 2
Views: 1072
Reputation: 376
This was a bug, as the Beta certificate was never deployed to the server. I have worked to get that added and now you should be able to use the sample code, as is, and download the certificate without receiving a 404.
Upvotes: 1
Reputation: 1054
Ok, I finally got this to work.
The link you posted with the b809.. id is for windows apps, not windows phone 8 apps. It appears the certificate is different.
The id from the test receipt you posted is the same I am getting in my beta app and I think it will be the same when we go out of beta.
Inside the example found here, in the zip file there is a file called IapReceiptProduction.cer. If you double click it and view details you will see it has a thumbprint that matches your certificate id.
I included that file in my solution and I load it using the sample code from my link and that works.
I just hope they wont change the certificate at some point.
EDIT: It appears the phone emulator does not get signed receipts (my working test was on an actual phone). The receipts I get in the emulator also have a different certificate id (FB3D3A6455095D2C4A841AA8B8E20661B10A6112).
Upvotes: 1