4 ms·
Doesn't explain the technical why it can't be fixed. Everywhere seems like another PR post. Anyone has a more detailed explanation?
by ksec 2y ago
Doesn't explain the technical why it can't be fixed. Everywhere seems like another PR post. Anyone has a more detailed explanation?
- nelwr 2y agoConsidering the timing (January 24th), it's probably related to Apple's switch from a SHA-1 signing certificate to a new SHA-256 one: https://developer.apple.com/documentation/technotes/tn3138-handling-app-store-receipt-signing-certificate-changes https://developer.apple.com/documentation/technotes/tn3138-h... It's possible their receipt validation code doesn't support SHA-256, and they can't/won't update it. Maybe the source code was lost, the team was disbanded, or they're just not bringing in enough iOS IAP revenue to justify the engineering cost.