Lich Bleach-SkullVerified account

@siegel @pschiller As far as I know customers have never received anything from Apple explaining these failures or how to resolve them.

@wadeco @siegel Failures you see only effect developers with WWDR intermediate cert installed, not users. Please remove from keychain to fix

@pschiller That may be a known cause, but we're seeing this from end users in the field. (Not arguing, just providing data.) // @wadeco

@siegel @pschiller I just ran into this issue with TextWrangler yesterday. Was 5.0.2 built using the now-expired WWDR cert?

@wadeco It was built on 2015-11-11, so likely so. // @pschiller

@siegel @wadeco I thought it wasn’t supposed to matter which certificate you had when the app was built, only that validation code works.

@mjtsai That was my understanding as well. // @wadeco

@pschiller …and time & time again, customers come to us angry about something we couldn't possibly have dealt with in advance. // @wadeco

@pschiller Today is likely a busy one for you, but I am delighted to have this discussion at any mutually convenient time. // @wadeco

It’s worse @siegel, I trashed BBedit and started using smth else. Not your fault, but this silent failed launch, MAS, … //@pschiller @wadeco

@robertvojta You can always ask for help, you know. :-) http://www.barebones.com/support/technotes/DamagedApp.html … // @pschiller @wadeco

@siegel I know, even that I can switch to non MAS version, … Hassle I do not want to go through. //@pschiller @wadeco

@robertvojta That doesn't really make any sense to me, but "you do you", as the kids say. :-) @pschiller @wadeco

@siegel no need to understand reasoning :-) I just wanted to point out that you lost customer, because of  & MAS. // @pschiller @wadeco