Post

Replies

Boosts

Views

Activity

Reply to TN3138: Handling App Store receipt signing certificate changes
We were caught unawares of this change due to a game of ours that validates the receipts locally. We are submitting a fix, but I wanted to understand why we were unable to detect the change earlier :- The Technote mentions that the certificates would change on :- Sandbox - June 20, 2023 TestFlight - August 16, 2023 App Store - August 16, 2023 We released an update on 2nd Sept 2023 which was still using the SHA-1 algorithms. That did not fail ; was there a delay in rolling out the new certificate on App Store? Even today (23rd Sept), the Sandbox and Testflight builds of the game, which use the SHA-1 algorithm to validate the receipt locally, validate successfully. Is there any other criteria being used to return the SHA-1 256 certificates on Sandbox or Testflight? e.g. to only devices running on iOS 16.6 etc ?
Sep ’23
Reply to TN3138: Handling App Store receipt signing certificate changes
We were caught unawares of this change due to a game of ours that validates the receipts locally. We are submitting a fix, but I wanted to understand why we were unable to detect the change earlier :- The Technote mentions that the certificates would change on :- Sandbox - June 20, 2023 TestFlight - August 16, 2023 App Store - August 16, 2023 We released an update on 2nd Sept 2023 which was still using the SHA-1 algorithms. That did not fail ; was there a delay in rolling out the new certificate on App Store? Even today (23rd Sept), the Sandbox and Testflight builds of the game, which use the SHA-1 algorithm to validate the receipt locally, validate successfully. Is there any other criteria being used to return the SHA-1 256 certificates on Sandbox or Testflight? e.g. to only devices running on iOS 16.6 etc ?
Replies
Boosts
Views
Activity
Sep ’23