You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2021. It is now read-only.
Using the verifyTransaction example from the readme results in the failure block always being called due to receiving a content type of text/plain from the Apple receipt server.
This is the error I get in the failure block of verifyTransaction:
Could the http client in CargoBay be made less strict so that it can accept a text/plain response? Seems like the json from Apple may be valid but doesn't have the correct header.
Only tested this in the Sandbox environment so maybe it's not an issue in production.
The text was updated successfully, but these errors were encountered:
Using the verifyTransaction example from the readme results in the failure block always being called due to receiving a content type of text/plain from the Apple receipt server.
This is the error I get in the failure block of verifyTransaction:
Error -1016 (Expected content type {(
"text/json",
"application/json",
"text/javascript"
)}, got text/plain)
Could the http client in CargoBay be made less strict so that it can accept a text/plain response? Seems like the json from Apple may be valid but doesn't have the correct header.
Only tested this in the Sandbox environment so maybe it's not an issue in production.
The text was updated successfully, but these errors were encountered: