Michael TsaiVerified account

@reneritchie I *think* that conflates two issues. "App is damaged" happens before launch, receipt verification is up to the app. // @mjtsai

@siegel @mjtsai There were two issues: failure to clear cache and SHA-2 not being supported, far as I know.

@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

@mjtsai You know, I'm not so sure it's a good idea to include the support email from a supposed "Apple Support" rep. I've had MANY emails..

@Dman228 You think the screenshot is fake? I tend to believe it, having seen many crazy Apple Support e-mails that my customers forwarded.

@mjtsai Its just the support email seems fishy to me

@dman228 @mjtsai Tho –IF– that email IS legit, I'd not be *surprised* nor would that change my deep concern position re: problems at Apple.

@dman228 @mjtsai I've said it often, many places…I've been through dark times with Apple before. Many look BACK and say "signs were there, …

@dman228 @mjtsai … but I didn't see them!" But the signs WERE THERE, and some DID see them. Signs have been here. Many signs.

@dman228 @mjtsai Most important of which is the hubris, the arrogance. Can't stress strongly enough how important a sign that was in '90s.