Re: Finding non-backwards compatible code
Re: Finding non-backwards compatible code
- Subject: Re: Finding non-backwards compatible code
- From: "Glenn L. Austin" <email@hidden>
- Date: Tue, 28 Aug 2012 21:39:30 -0700
On Aug 28, 2012, at 7:14 AM, Owen Hartnett < email@hidden> wrote: Hi all:
Just had a debug session where a user brought in an iPad running ios 4.3.2 and was crashing. Turns out we had a couple of ios 5.0 only calls to UITabBar in there. Our bug, obviously, and easy to fix with a couple of respondToSelectors. But there really isn't a good mechanism for finding these once you've written that code. Our app says we're supposed to run on 4.3.2 on up. The compiler settings we're using think self.tabBar.tintColor is good stuff, so we get no warnings or errors, even if I build for simulator 4.3. How do you guys comb through your code looking for methods that are later then your lowest running system? Do you set the compiler to build for the low end system or is there a better way?
Personally, I change the base SDK for the project to the minimum SDK and rebuild -- and then fix all of the errors.
-- Glenn L. Austin, Computer Wizard and Race Car Driver <><
"Where there's breath, there's hope!"
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden