It's not really an API issue, it's how iOS vs Android talks to the web. All web-enabled apps are going to stop working when the vendor stops updating, but I could at least use my MotoG's browser right up until the certs expired. The rendering ending in iOS is so old that it's starting to choke on websites.
I think you're missing it. How it works now:
phone (api 3.x) -> server (api 3.x) : works phone (api 3.x) -> server (api 4.x) : does not work phone (api 3.x) -> proxy (understands api 3.x speaks api 4.x) -> server (api 4.x) : works
I'm talking about browsers and their ability to communicate with the web be it lack of certificates or because the browser doesn't support newer conventions.
I have no idea what you're talking about. What API? What program or website are you using?
It works for certificates too.
Some times the issue is that certificates expire. Some times the issue is that the API changes and the app hasn't been updated to use the new API. It doesn't matter what the application in question is, and I'm not talking about any one in particular.
(post is archived)