I've had more fragmentation problems with iOS/iPhone than with Android
1–10 of 51 posts
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#2'I found some potential problems in my app, fixed them and posted an update'
'Of course this was a time when Apple approved an update fast and it went out before I could test and I had not fixed all the issues.'
'I must have fumbled in the SVN check in.'
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#3'I found some potential problems in my app, fixed them and posted an update' 'Of course this was a time when Apple approved an update fast and it went out before I could test and I had not fixed all the issues.' 'I must have fumbled in the SVN check in.'
So initially there were problems with the code and afterwards with his development process.
I fail to see what this got to do with iPhone vs. Android. It could have happened with both platforms.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#4'I found some potential problems in my app, fixed them and posted an update' 'Of course this was a time when Apple approved an update fast and it went out before I could test and I had not fixed all the issues.' 'I must have fumbled in the SVN check in.'
So initially there were problems with the code and afterwards with his development process. I fail to see what this got to do with iPhone vs. Android. It could have happened with both platforms.
His point is that Android made it easy to test multiple platforms, and Apple did not.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#5> 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.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#6The problem is that Apple deprecates their SDK really quickly. As developers, that makes it really tough to test old versions of iOS when installing an updated SDK REMOVES previous versions!! Even if you select an older "OS Deployment Target", you're out of luck unless you have a device to test it on. The Simulator is always running the latest version.
I guess they assume everyone will upgrade, but a lot of people don't or can't.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#7> 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 method…
Exactly. In this case, the developer should've either tested prior to release (on 3.0), or specified a 4.0 build.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#8The problem is that Apple deprecates their SDK really quickly. As developers, that makes it really tough to test old versions of iOS when installing an updated SDK REMOVES previous versions!! Even if you select an older "OS Deployment Target", you're out of luck unless you have a device to test it on. The Simulator is always running the latest version. I guess they assume everyone will upgrade, but a lot of people do…
It's tricky. I wish they made it easy to downgrade to other iOS versions as well.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#9The problem is that Apple deprecates their SDK really quickly. As developers, that makes it really tough to test old versions of iOS when installing an updated SDK REMOVES previous versions!! Even if you select an older "OS Deployment Target", you're out of luck unless you have a device to test it on. The Simulator is always running the latest version. I guess they assume everyone will upgrade, but a lot of people do…
> The Simulator is always running the latest version.
Actually this appears to be false now. I just fired up my iOS Simulator, and in the "Hardware" menu I can select which OS version I want, either 3.2, 4.0.2, 4.1, or 4.2.
Re: I've had more fragmentation problems with iOS/iPhone than with Android
#10The problem is that Apple deprecates their SDK really quickly. As developers, that makes it really tough to test old versions of iOS when installing an updated SDK REMOVES previous versions!! Even if you select an older "OS Deployment Target", you're out of luck unless you have a device to test it on. The Simulator is always running the latest version. I guess they assume everyone will upgrade, but a lot of people do…
> The Simulator is always running the latest version. Actually this appears to be false now. I just fired up my iOS Simulator, and in the "Hardware" menu I can select which OS version I want, either 3.2, 4.0.2, 4.1, or 4.2.
That's right you can select all those versions accept 3.1.3 and that is the problem.