I updated the MAS post with more tweets and some notes about what Apple Support is telling customers: http://mjtsai.com/blog/2015/11/12/no-one-minding-the-store/ …
-
-
0 replies 1 retweet 3 likes
-
@reneritchie I *think* that conflates two issues. "App is damaged" happens before launch, receipt verification is up to the app. //@mjtsai0 replies 0 retweets 1 like -
@reneritchie@mjtsai Sure. But SHA-2 non-support wouldn't cause the "app is damaged" error, AFAIK.0 replies 0 retweets 0 likes -
@siegel@reneritchie@mjtsai receipt validation failure would cause an app to exit with code -173, which should cause that error message.0 replies 0 retweets 1 like -
@tapbot_paul I believe exit(173) triggers store signin, but that's after launch too, right? //@reneritchie@mjtsai0 replies 0 retweets 0 likes
@siegel @tapbot_paul @reneritchie That was my understanding. I thought when you get App Damaged it doesn't even run your code.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Michael Tsai
Rene Ritchie
Lich Bleach-Skull
Paul Haddad