iOS causes existing apps to crash

It has nothing to do with programming skills. I fixed my apps now. The point is that one does not have to constantly fix and maintain the code just because of operating system upgrade. ID rather spend time doing something more productive such as getting bbbj from becky goldmine. In windows, old programs still work on new OS, just looks old but does not crash.
 
I've heard a lot of people are experiencing this problem.

Yes, I found it humorous as well: The Comical Irony That iOS 7 Users Are Suffering From Blue Screens Of Death
link: http://techcrunch.com/2013/10/11/th...ers-are-suffering-from-blue-screens-of-death/

I agree that new OS can't stifle progress by waiting for old software to be updated. Some companies may not exist anymore others have dropped support on an aging software product. I am guessing that Apple (like any other OS developer) measured the impact and decided to move forward even if a few software packages can't be supported.

I'm not sure if Apple is entirely legally free in the event of a catastrophic failure since they have the unique position that all software was purchased through their site so that they can make revenue from it.
 
Apple have taken the view that deprecating (and removing) old interfaces from the API is a "good thing" to avoid OS bloat and half-implemented features across multiple platforms.

It was an okay approach when there were only two or three platforms, but now that there are iPhone 3, 3G, 3GS, 4, 4S, 5, 5S, 5C, various generations of iPad and iPad mini to contend with "in the field", the number of configurations which require some degree of support has grown significantly and everybody ends up screwed.

Unfortunately, there are no complete solutions: while Apple have started allowing developers to have "older" versions of an app in the App Store, it's difficult to manage and impossible to test correctly. And offering an App which only runs on the latest platforms is extremely limiting and rather expensive as a development rule.

If you find an actual solution (other than only releasing the simplest apps which don't make use of different features), others would also be glad to hear about it.
 
Apple cares about Apple. They could really give a flying shit about its customers, only as long as the stores keep busy, that's all they care about.
That's like any other corporation really.

I'd say the customer sat scores are not well aligned with your point of view…

acsi_macs-800x335.jpg
 
Apple have taken the view that deprecating (and removing) old interfaces from the API is a "good thing" to avoid OS bloat and half-implemented features across multiple platforms.

It was an okay approach when there were only two or three platforms, but now that there are iPhone 3, 3G, 3GS, 4, 4S, 5, 5S, 5C, various generations of iPad and iPad mini to contend with "in the field", the number of configurations which require some degree of support has grown significantly and everybody ends up screwed.

Unfortunately, there are no complete solutions: while Apple have started allowing developers to have "older" versions of an app in the App Store, it's difficult to manage and impossible to test correctly. And offering an App which only runs on the latest platforms is extremely limiting and rather expensive as a development rule.

If you find an actual solution (other than only releasing the simplest apps which don't make use of different features), others would also be glad to hear about it.

You have a valid point about deprecating old APIs to keep the overall system clean and efficient. However I'm not talking about deprecated APIs though. The specific bug I had was popup windows spawned from a non-UI thread. While it worked perfectly in pre-6.1, in 7.0, it just crashes without warning. No API used in this code has been officially changed or deprecated, the new iOS just decided to behave differently to the same API used previously in 6.1 and 6.0, and not documented at all, and not give developers any warnings. I know of a few other cases like this.

If you've been working on software like me for a while you'd never come to expect something like this from a reputable platform. I worked on Unix, MS Visual studio, Java. Yes they all deprecated old APIs over time, but it all had a clearly defined transition from one OS to the next. Apple seems to be so cocky that they think they can just "PUSH" the recommended new paradigm onto everyone and not do the work on testing it, - oh and "PUSH" the testing work on the 3rd party developers because they all have NO CHOICE but listing their business on Apple app-store!
 
No HDMI? That is a universal input except in the Mac universe.

It is their attempt to corner the smart TV market backfiring. Seriously, if they could do away with their own USB port they would too. and they would change its size and pin count slightly every 2 years so you are FORCED to upgrade.
 
Speaking of "FORCE"didn't they change a cable for their iPhone and screw over a ton of their customers who bought docks, cables, etc?
Really didn't follow it, but I do remember people moaning and griping on about it.
http://www.gizmodo.com.au/2013/08/apple-still-has-a-problem-with-lightning-cables/
Was the above it? Or was this entirely different?

I don't really follow them. don't really care for their products beyond what I have to for work. I wish they shrink back to 1% market share so I don't have to worry about developing for Apple platform anymore.