Hannes Oud

We'll merge this after my vacation, just in case it causes any unexpected troubles

> First and foremost, thank you for creating this useful library! much appreciated! Oh, good catch! That looks like a bug/regression that might have crept in when moving away from...

Looking at https://www.objc.io/issues/17-security/receipt-validation/ it seems we are doing the **integrity** check might be omitting the **authenticity** check.

There's no update (the issue still exists)

thanks for the update and the info on storekit testing! > you could remove the option for configuring a custom certificate. sounds like a good idea

It seemed less complicated than I thought, I think I found a way to do the missing authenticity check, should also work with custom supplied root certificates (allthough probably not...

Thanks for the feedback, this aligns with how we handled it too.

Workaround (relevant on macOS only): If the receiptValidation fails with `.incorrectHash`, then try again using `getLegacyPrimaryNetworkMACAddress` as device identifier. ```swift // validate let result = AppReceiptValidator().validateReceipt(parameters: .default) #if os(macOS) if...

Here‘s a way to get the info: $ sw_vers; xcodebuild -version; https://twitter.com/olebegemann/status/918190328611471360

> Is this workaround still needed? Good question! I can't answer it because we unfortunately have no data collection in place to establish if this workaround still gets active for...