{"id":36294,"date":"2022-06-22T16:43:49","date_gmt":"2022-06-22T20:43:49","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36294"},"modified":"2023-05-29T10:16:02","modified_gmt":"2023-05-29T14:16:02","slug":"broken-renewal-of-mas-receipts","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/06\/22\/broken-renewal-of-mas-receipts\/","title":{"rendered":"Broken Renewal of MAS Receipts"},"content":{"rendered":"

Lukas Kubanek<\/a> (FB9789052, tweet<\/a>):<\/p>\n

I started integrating on-device App Store receipt validation into my Mac app, currently not utilizing StoreKit for any kind of in-app purchases. I followed the documentation and employed a check that calls exit(173)<\/code> if the receipt is invalid. According to the documentation, this should trigger a renewal of the receipt. When I launch the app from Xcode’s build folder for the first time, I get correctly presented with the App Store login window. After entering credentials of a sandbox user configured in App Store Connect, the app quits, relaunches, and then the following dialog appears:<\/p>

“MyApp” is damaged and can’t be opened. Delete “MyApp” and download it again from the App Store.<\/p><\/blockquote><\/blockquote>\n

This has been broken since around the release of Monterey. This makes it impossible to test the Mac App Store builds of my apps before submitting them to the store. Fortunately, my receipt validation code is already written and working reliably, because I don’t know how I could fully test it without being able to download a receipt.<\/p>\n\n

The mentioned issue doesn’t only occur in the sandbox but also for production apps. When removing the _MASReceipt<\/tt> folder from the production app, it’s supposed to renew the receipt when launched. Instead, the same dialog informing about the damaged app is shown, and the app has to be re-downloaded entirely from the Mac App Store.<\/p><\/blockquote>\n\n

Previously:<\/p>\n