Nothing to do with Apple? Since iOS7, Apple is constantly breaking apps that are already in the store and running fine. This is because they don't provide a backwards compatible runtime. For example, your app that's compiled and working well for iOS 8.2 can have new bugs (like text fields not appearing) after the user upgrades to iOS 8.3. To re-iterate, the user has not re-installed your app. They are still using the same great app compiled for 8.2 and now it doesn't work correctly. And the bug is caused by bad code from Apple in their runtime. To use an ironic comparison, if you made a Flash game in Flash 9, it would always run exactly the same way until the end up time, even after Flash 13 is released, because Adobe/Macromedia kept the runtime for each version and did not change it after it was released. New version meant a new runtime engine.
Anyway, so Apple breaks your app. It's possible you don't notice this because you don't test every feature of every app you've created for every new iOS version on the day it comes out. So within a couple weeks, most of your clients are asking you why your app doesn't work and you have to scramble to replicate the problem and then someone how fix it, sometimes having to rewrite a core part of your app. This happens over and over and it's tiring, costs your company money, makes you look bad to your clients and is very demoralizing. This is no one's fault but Apple's.
Anyway, so Apple breaks your app. It's possible you don't notice this because you don't test every feature of every app you've created for every new iOS version on the day it comes out. So within a couple weeks, most of your clients are asking you why your app doesn't work and you have to scramble to replicate the problem and then someone how fix it, sometimes having to rewrite a core part of your app. This happens over and over and it's tiring, costs your company money, makes you look bad to your clients and is very demoralizing. This is no one's fault but Apple's.