verifyReceipt is providing strange results lately in the sandbox environment. Instead of returning the expiration time of the latest receipt in returns something from the past The [pending_renewal_info] returns multiple entries and none of them are for the current receipt Any one experiencing the same issues?

Hi, Starting this weekend our backend fails to connect to the production Apple verifyReceipt endpoint. It's a C# .NET service running on windows server. The full exception received is: Exception: "The underlying connection was closed: An unexpected error occurred on a send". Inner Exception: "Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host". Is someone else facing a similar issue? sending a request to the Apple production verifyReceipt URL via Postman (located on the same server) succeeds. Thanks in advance...

Hi, We are using subscription. In the last past several days VerifyReceipt returns multiple entries in the Latest_receipt_info array although we pass exclude-old-transactions=true (this occurs on both sandbox and production environments). Noticed that this occurs for subscriptions that have been upgraded/downgraded.