Nobody likes an error message, including developers, which is probably why iOS app makers were chatting on social media about how Apple recently responded to some of their complaints.
The company recently updated its security certificates a number of weeks ago, but some problems with caching led a number of iOS developers to experience receipt verification failures when they were putting their apps in the App Store. A letter that was posted to an online forum suggested the problem was more or less resolved, but that they should be monitoring for any additional glitches.
iOS devs sounded like they were surprised it took Apple so long to explain itself:
https://t.co/exmaVs01Se finally a response
— franz (@neozeed) November 18, 2015
Others wondered why Apple wasn't more advanced from a security perspective:
isnt OpenSSL deprecated by apple for yew years now? time to follow own guidelines https://t.co/8Oc0ql2eUI
— Marcin Krzyzanowski (@krzyzanowskim) November 18, 2015
@krzyzanowskim They deprecated the system shared library in favor apps statically linking to a known version. See: https://t.co/xziYZyaCUa
— iOS Developer Zone (@iOSDevZone) November 18, 2015
There were also plenty who suggested they were still dealing with the certificate snafu:
Apple Responds to Devs Re: Expired App Store Certificates https://t.co/7oD1WNS3ZF via @MacRumors // still have a few apps hitting this :I.
— Tom McFarlin (@tommcfarlin) November 18, 2015
Not everyone was ready to jump on Apple, though, especially since it took the time to send the letter:
Can you guys stop bitching that Apple wasn't doing anything about this now? https://t.co/vuROgcIa1T
— Robert DeLuca (@robdel12) November 18, 2015
As Apple continues to expand into new product lines, however, the company may need to step up its response time:
Can't wait for the day when your car won't start because Apple forgot to renew their security certificates.
— Cristian Radu (@cristianradu) November 19, 2015