Code 173 no longer triggers receipt generation

Question

Created Mar ’21

Replies 16

Boosts 0

Views 5.4k

Participants 15

My macOS application exits with code 173 when the Mac AppStore receipt validation fails. This used to trigger a system dialog that allowed me to enter test user credentials which then created an AppStore receipt. Now this behaviour changed to just showing a dialog stating that the application is damaged and needs to be redownloaded from the AppStore. This makes it impossible for me to test receipt validation for my app.

What might have caused this change in system behaviour? I'm even getting this "damaged application" dialog when I delete the "_MASReceipt" folder from third party applications when I'm pretty sure that before it also showed this dialog that allows to enter AppStore credentials and recreate a valid receipt.

Answered by Schubert in 702880022

It's now working again.

Boost

Answer 1

janice OP

Jun ’22

Not working again. No change to macOS version nor Xcode version. Just back to these console messages:

error	11:59:51.470396-0700	storeuid	<ReceiptRefreshRequest: 0x1581c3ee0>: Error fetching receipt for com.moremobilesoftware.divelogdt - Error Domain=com.apple.commerce.server Code=1008 "(null)"
default	11:59:51.471332-0700	storelegacy	StoreLegacy: Failed to renew receipt for application at path /Users/jXXXXXXX/Library/Developer/Xcode/DerivedData/<Product>/Build/Products/Debug/DiveLogDT.app : 'The operation couldn’t be completed. (com.apple.commerce.server error 1008.)'

Anyone else seeing it go back and forth and back and forth like this?

0