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
I’ve been using TPInAppReceipt prior to the 3.4.1. update. With the 3.4.1 update I notice the Validation: verifySignature() function has changed.
Previously while in DEBUG mode, the checkChainOfTrust() function was not called. The 3.4.1 version does not bypass the checkChainOfTrust() for debugging which results in the receipt.validate() to throw a IARError.validationFailed(reason: .signatureValidation) error.
My question is should the IARError.validationFailed(reason: .signatureValidation) error be ignored during debugging? Or has something else changed that needs to be addressed for debugging?
Thank you for creating and maintaining the TPInAppReceipt code base. Your time and effort is appreciated.
Regards,
The text was updated successfully, but these errors were encountered:
Hello,
I’ve been using TPInAppReceipt prior to the 3.4.1. update. With the 3.4.1 update I notice the Validation: verifySignature() function has changed.
Previously while in DEBUG mode, the checkChainOfTrust() function was not called. The 3.4.1 version does not bypass the checkChainOfTrust() for debugging which results in the receipt.validate() to throw a IARError.validationFailed(reason: .signatureValidation) error.
My question is should the IARError.validationFailed(reason: .signatureValidation) error be ignored during debugging? Or has something else changed that needs to be addressed for debugging?
Thank you for creating and maintaining the TPInAppReceipt code base. Your time and effort is appreciated.
Regards,
The text was updated successfully, but these errors were encountered: