App rejected for receipt validation failure

I had an app update get rejected with:


>We noticed that with a valid receipt installed, your app quits on launch. The Console reports the app "Exited with exit code: 173" and the OS states the app "is >damaged and can't be opened". This generally indicates that the app is not verifying its receipt correctly.


I have not changed my receipt validation code from previous releases (which were approved). In this particular app, I exit(173) only if the following is true:

1. There is no receipt on the main bundle.

2. If Apple's servers say the receipt is no good.


Other than that, I don't do local receipt validation on this app. I've gotten this rejection before on another app a couple of months ago. I couldn't figure out what was causing the issue, so I simply cleared derived data, re-archived and submitted again (and it was approved). I'm wondering if anyone else has experienced this before too?

Deleted derived data, rearchived, and submitted with no code changes and the app passed review. Not sure if it's a compiler issue or a codesigning issue when uploading...or if it has something to do with how they test the receipt on their end. It seems unlikely that I'd be able to provide sufficient information to reproduce the bug, so I'm not going to file this one.

Happened again. Same thing. Deleted derived data, resubmitted, and accepted.


I find myself having to throw away about 20 minutes of work time resubmitting an update, and of course this delays an app update from being released.


Has anyone else had this happen to them?

Happened to me as well - a clean build fixed it. Thanks for finding this!

App rejected for receipt validation failure
 
 
Q