Hacker News new | ask | show | jobs
by hboon 5580 days ago
Maybe the executable name doesn't match the plist's entry or the app store receipt doesn't match?
1 comments
EGreg 5580 days ago
According to this, it sounds like it's Apple's fault:

http://getsatisfaction.com/firemint/topics/it_wont_start_on_...

The "receipt" file generated by Mac App Store should have been called Receipt. On case sensitive file systems, the users will get the nasty error.

What I don't understand is, what fixes have the developers made in the update they submitted to apple, so that it works?

Here is another one: http://pariahware.com/blog/?p=359

Any ideas?

link
hboon 5580 days ago
It is ".../SampleApp.app/Contents/_MASReceipt/receipt" (lowercased r) according to http://developer.apple.com/devcenter/mac/documents/validatin...

My guess is your (as well as those links above) development and testing platform is case-insensitive and thus missed this.

link
EGreg 5580 days ago
yeah. But the weird part is that we were testing for exactly that!

Contents/_MASReceipt/receipt

and returning 173. Now we are going to be looking for that, and if not found, try looking for /Receipt.

According to http://getsatisfaction.com/firemint/topics/it_wont_start_on_... it is actually Receipt.

I don't know, which one is it? I am worried that it might be one of the OTHER places where 173 is being returned. Such as if Apple's Root CA is missing.

I thought that whole /receipt thing as autogenerated by apple.

link
EGreg 5580 days ago
I FIGURED IT OUT!!

Apple signs with their own certificate when posting on the MacOS store. We were checking for OUR own certificate (the one we used to sign when submitting to Apple.)

link