{"id":45438,"date":"2024-10-18T14:29:02","date_gmt":"2024-10-18T18:29:02","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=45438"},"modified":"2025-03-18T11:12:29","modified_gmt":"2025-03-18T15:12:29","slug":"exit173-receipt-fetching-deprecated-on-sequoia","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/10\/18\/exit173-receipt-fetching-deprecated-on-sequoia\/","title":{"rendered":"exit(173) Receipt Fetching Deprecated on Sequoia"},"content":{"rendered":"

Jeff Johnson<\/a> (Mastodon<\/a>):<\/p>\n

[If] you compile your app with the macOS 15 SDK in Xcode 16, and your app exits with the status 173—the traditional way to handle Mac App Store receipt validation failure—then macOS 15 Sequoia will show the user an alert[…]<\/p>

The alert is terrible for at least two reasons. First, the text is total nonsense to end users and meaningful only to app developers. Second, the text is inaccurate. Exiting with status 173, for example returning 173 from the main()<\/code> function, still works! A new, valid Mac App Store receipt will be fetched, if possible. In this respect, the only difference between Sonoma and Sequoia is that Sequoia shows the annoying, confusing, inaccurate alert to the user.<\/p>

As far as I’m aware, the new macOS 15 behavior has not been documented by Apple anywhere<\/em>.<\/p><\/blockquote>\n

The WWDC session<\/a> only<\/a> says<\/a>:<\/p>\n

If your app still uses the Original API for In-App Purchases, I have an important update to share with you. Beginning with iOS 18 and aligned OS releases, the Original API for In-App Purchase is deprecated, including the unified receipt. Your existing apps will continue to work, but the legacy API won’t receive any enhancements or new features in future operating system releases.<\/p><\/blockquote>\n

But this doesn’t mention the scary alert, and it’s not obvious that exit(173)<\/code> is part of the IAP API because it was introduced for up-front purchases before IAP even existed.<\/p>\n

Johnson has investigated the documentation history. Apple no longer mentions exit(173)<\/code> at all, never saying that it was deprecated, and the current documentation<\/a> recommends using StoreKit 1, which is is deprecated<\/a>.<\/p>\n

According to the WWDC session, Apple wants apps to switch to StoreKit 2<\/a>, which is a Swift-only API. Apps targeting older versions of macOS would need to bundle the entire Swift runtime just to download the Mac App Store receipt.<\/p>\n

It’s not yet clear<\/a> to me whether Sequoia shows the alert for apps (linking with the macOS 15 SDK) downloaded from the App Store or only when testing such apps. I presume it’s only the latter because I have not seen a huge outpouring of users mentioning the alerts. However, it’s also possible that few apps have been shipped using Xcode 16 so far, e.g. because doing so will make apps that use Quick Look crash<\/a>.<\/p>\n\n

Previously:<\/p>\n