4 ms·
> I was not worried about breaking it again as the changes in this update did not touch anything that had issues before...I must have fumbled in the SVN check i
by aaronbrethorst 16y ago
> I was not worried about breaking it again as the changes in this update did not touch anything that had issues before...I must have fumbled in the SVN check in.
Even if this wasn't the case, it's always possible that some new chunk of code you're adding requires a library that doesn't exist on down-level OS versions. Or the new code doesn't properly check existing libraries for the availability of classes or methods (e.g. some UIKit classes only exist in iOS 4.0 and up. To ensure that your app doesn't crash on older versions, you need to test for the existence of the class you want to instantiate). If any of these conditions hold true, crash city.
I own every iPhone that Apple has released, and I keep my original iPhone on 3.1.3 for precisely this kind of scenario. In fact, just yesterday I had to fix a couple iOS 3.1.3-specific bugs, and couldn't have done it without that original iPhone.
Long story short: if you're going to claim you support a particular platform, you better test on it. If you can't or won't test on it, then don't support that platform as a deployment target.
- nhangen 16y agoExactly. In this case, the developer should've either tested prior to release (on 3.0), or specified a 4.0 build.