Michael Tsai
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/ …
Rene Ritchie
Lich Bleach-Skull@reneritchie I *think* that conflates two issues. "App is damaged" happens before launch, receipt verification is up to the app. // @mjtsai
-
-
-
@reneritchie@mjtsai Sure. But SHA-2 non-support wouldn't cause the "app is damaged" error, AFAIK. -
@siegel@reneritchie@mjtsai receipt validation failure would cause an app to exit with code -173, which should cause that error message. -
@tapbot_paul I believe exit(173) triggers store signin, but that's after launch too, right? //@reneritchie@mjtsai - View other replies
-
@siegel@reneritchie@mjtsai yeah but I think all this stuff from this week is 173, that’s why some apps don’t have a problem. -
@tapbot_paul For us it was all fail to load, no 173 exits I can recall. //@reneritchie@mjtsai -
@siegel@reneritchie@mjtsai I still haven’t rebooted, seeing 173 on launching some apps that handle things properly. - View other replies
-
@tapbot_paul That is most peculiar. :-\ +@reneritchie@mjtsai
-
-
@reneritchie I think@siegel is right. Your OpenSSL/SHA-2 theory would seem to predict that my apps wouldn't launch, but they do. -
@reneritchie Don't hold me to that, though. :-) //@mjtsai
Paul Haddad
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.