fix: Catalyst platform

[tikhop]

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

[tikhop]

@metadynesoftware here is the fix - I have also added an additional job that checks that library compiles for catalyst.
Thank you!

[metadynesoftware]

Great! The 4.0.1 update compiles for Catalyst. I still have to complete the migration to 4 before proceeding with additional testing. Thanks again, Best regards,

…

On Feb 4, 2026, at 10:38 AM, tikhop ***@***.***> wrote: tikhop left a comment (tikhop/TPInAppReceipt#138) <#138 (comment)> @metadynesoftware <https://github.com/metadynesoftware> here is the fix - I have also added an additional job that checks that library compiles for catalyst. Thank you! — Reply to this email directly, view it on GitHub <#138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHJY6S4JZLKRLRQIJZEYLH34KI4D5AVCNFSM6AAAAACT7QSMQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBYG44TQNJRGI>. You are receiving this because you were mentioned.

[tikhop]

@metadynesoftware Great, thank again!

Let me know if you have any questions, there is guide how to migrate. In general, not so much changed from the client perspective.

[metadynesoftware]

Hi, After integrating version 4.0.1 with the assistance of the migration guide, an issue has arisen. For background, the project was Swift 6 so the migration was relatively easy as outlined. However, in the TPInAppReceipt code at: public func validate(_ receipt: any ReceiptValidatable) async -> VerificationResult { await withTaskGroup(of: VerificationResult.self) { group in for verifier in verifiers { group.addTask { await verifier.verify(receipt) } } for await result in group { if case let .invalid(error) = result { group.cancelAll() return .invalid(error) } } return .valid } } The return result always fails with an: invalidCertificateData response. Because this is an existing app/project, the 3.4.1 version suggests the certificate is valid. Testing is on a physical device (iPad), everything is running the latest OS and Xcode versions. Bypassing the validation step by processing the receipt finds the relevant purchase information suggesting the receipt itself is operating as expected but the certificate verification is the issue. The validation process appears to have been entirely re-written so debugging for comparison is not easily performed. Is there an issue with the certificate validation process or possibly some other testing issue as relates to the certificate validation? Best regards,

…

On Feb 4, 2026, at 6:08 PM, tikhop ***@***.***> wrote: tikhop left a comment (tikhop/TPInAppReceipt#138) <#138 (comment)> @metadynesoftware <https://github.com/metadynesoftware> Great, thank again! Let me know if you have any questions, there is guide how to migrate. In general, not so much changed from the client perspective. — Reply to this email directly, view it on GitHub <#138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHJY6SZH73KLKSBJIKRJQDL4KKQZLAVCNFSM6AAAAACT7QSMQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNJQGY3TCNZWGM>. You are receiving this because you were mentioned.