Hi All,
We are trying server-to-server notifications for in-app purchases. This is the first time we are configuring in-app purchases for the app, so configurations are still for test apps and in-app purchases being tested by sandbox accounts.
For server-to-server notification, we configured the url as mentioned in the doc, but still, our server url is not being called after a successful in-app purchase. Could you please help if anything more is required for config?
We have used both v1 and v2 notifications and we are using Consumable IAP. Note that we have used Test notification to make sure if our server is not blocking something, and have received it successfully
We are having the same issue on our side with our server properly accepting TLS V1.2 connections.
However validating the TEST notification, the response was a "firstSendAttemptResult": "TLS_ISSUE".
Here's the CURL information to our server (domain redacted).
* Connected to ***.*** (***.***.***.xxxx) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=xxxxxxx
* start date: Feb 28 00:00:00 2023 GMT
* expire date: Feb 28 23:59:59 2024 GMT
* subjectAltName: host "xxxx" matched cert's "***"
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify ok.
> GET / HTTP/1.1
Can you help us clear that issue? Thanks
Me too,I validate the TEST notification, the response was a "firstSendAttemptResult": "TLS_ISSUE". when I use 'curl -v' commond to connect the endpoint of my server:
About to connect() to ..*** port 443 (#0)...
Peer's Certificate issuer is not recognized.Closing connection 0curl: (60) Peer's Certificate issuer is not recognized. Did you solved the problem?
We are have the same issue as @martin_bwl. In Our case the curl connection to our server is: Trying 34.102.3.92:443...
-
—
App Store Commerce Engineer
-
—
pankaj_propertyguru
-
—
pankaj_propertyguru
Add a CommentHello! Are you using App Store server notifications V2 or V1? Have you tried requesting a TEST notification? What type of IAP are you testing?
Following are the required details
We have used both v1 and v2 notificationsWe have used Test notification, and have received it successfullyWe are using Consumable IAPRewriting the above comment. We tried both V1 and V2. And we are using Consumable IAP. Note that we have used Test notification, and have received it successfully