Hacker News Reader

Comment by EGreg | Hacker News Reader

Thanks guys. Listen ... I had to pull this app's availability on the app store, because almost everyone is getting the following message:

"Calendar.app" is damaged and can't be opened. Delete "Calendar.app" and download it again from the App Store.

This is horrible. We could have made so much good with this app, it's #1 in the productivity category, but because of this one thing, it's going to get bad reviews. Now when we release it, I doubt it'll be number 1. SUCKS!!!! SO MUCH!!!

I'm not sure what is causing this bug. Can anyone help? I am going to email apple support tomorrow and try to get them to expedite an update as much as possible. Has anyone any idea what could be causing this? I could use all the help I can get right now.

View on HN

Hope you can fix it soon. Here are some ideas:

Did you verify receipts in your app? If so, could this be the problem?

http://forums.realsoftware.com/viewtopic.php?f=7&t=37309

"I had mistakenly used the app name instead of the app bundle id in the verifytools receipt check code. "

Also, does anything show up in the system Console?

Did you do anything special to compile/package the app beyond regular Xcode + "Build and archive"?

Ouch. Oh, I feel so bad for you ... that would really be maddening to happen just when your app is rising on the app store. Hope you can get it fixed quickly and it doesn't damage too much!

Have you checked out the crash reports in iTunesConnect? They are under [Your App] -> view details -> crash reports

There are no crash reports. I don't think the app even gets launched. It has something to do with the bundle maybe?

http://grab.by/9gmN This is the only clue I have.

Maybe the executable name doesn't match the plist's entry or the app store receipt doesn't match?

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?

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.

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.

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.)

Reply on news.ycombinator.com