6 ms·

I think, Apple's general approach is:"We can break it." Documented or not. Seems like they change stuff all the time. Especially on iOS.

• WA 12y ago
  I agree. I think there was never a major iOS release that didn't break things in my app. Really basic stuff like a text input for example.
• valleyer 12y ago
  Can you provide examples of non deprecated API that Apple broke?
  • interpol_p 12y ago
    The recent Swift 1.2 release brought a whole load of code breaking changes. None of Swift 1.0 was explicitly deprecated.
    • Sephiroth87 12y ago
      That's a bit different, they explicitly said Swift is a work in progress and code compatibility is not guaranteed between versions...
      • Zikes 12y ago
        After 1.0 API changes really should increment the major version.
        • ebbv 12y ago
          Unless you say "We're probably going to break things." when you announce it, which they did.
          • cozzyd 12y ago
            Perhaps they should have chosen a more appropriate version number then.
            • zwily 12y ago
              Apple doesn't claim to do semver
              • Zikes 12y ago
                Regardless, that is what developers have come to expect. Not that semver is adopted wholesale, but at least don't break the API without incrementing the major version.