This problem was highlighted the other day in an update to Michael Tsai's earlier blog post about “Damaged” Mac App Store Apps, but I think it's important enough to warrant a dedicated blog post, because Mac developers who missed the update need to know about it. The problem is that 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 ...