pgagoober
Site Sponsor
- 415
- AZ
- BadManTurismo
I have this app on my wife's ipad and is working great. I had my wife use her account to download to my old iphone version 4.2.1 so I don't have to borrow her ipad when she's on it and I'm trying to work on a tune. When I tap the setting button it does nothng but goes back to the home screen. Is this one of the bug you are referring to?
Yes, I'm afraid so. It is fixed in version 1.02 and should be approved and released by Apple sometime next week.
For those interested in the boring details of how I managed to screw this up: Apple seems to have a policy of pushing developers to always develop for the latest version of iOS and as such they no longer provide a means to test apps on iOS 4.x via the simulator. Apple's advice for supporting older devices is to always build with the latest SDK and set your deployment target to the earliest version of iOS you wish to support. I made the mistaken assumption that by following this advice the development environment would warn me if I was using APIs that were not supported on my deployment target iOS. It does not.
The app was tested on iPhone 3GS, iPhone 4 and iPhone 4S before release, but because Apple also does not allow a developer to install earlier releases of iOS on a device I did not test on a physical device running 4.x. In retrospect this was clearly a bad mistake on my part. I knew I was not using any hardware-dependant features so I did not expect to run into any problems with older hardware that I did not have in-hand for testing. Needless to say as soon as the first bug report came in, I jumped on Craigslist and scrambled to get my hands on a 3G.
Wanna know the big problem that caused the crash? Setting a color on a button As frustrating as it must be for iOS 4.x users to encounter this problem, believe me I'm right there with you. Nonetheless it was clearly my fault and I apologize once again that this happened.
This experience makes me very concerned about developing a version for Android, which currently runs on in excess of 1300 devices and multiple vendor-specific versions of the OS! Trying to create a high quality and reliable app on such a fragmented platform is a scary prospect to say the least I certainly have made no decision on that yet but it would be a very expensive development process in both time and money, so the business case for it will need to be loud and clear. I don't need to make money from it but I would at least need to break even and more importantly not damage the reputation of the app by having it crash on devices that I cannot possibly hope to test. I think every developer is hoping Google somehow find a way to get control of this situation. I sincerely hope that happens soon.