Why does setting the deployment Target to 3.0 in X-Code 4.1 make all deprecations go away

Get Started | Login

Discussion Forums > Uncategorized

Replies: 4 Views: 223

stevek Aspiring developer Posts: 808 Reg: Dec 24, 2011 great neck 8,080	confirm \| cancel 01/13/12 04:41 PM (14 years ago) Why does setting the deployment Target to 3.0 in X-Code 4.1 make all deprecations go away The topic pretty much says it all. When I changed the deployment target to 5.0, got lots of yellow warnings about deprecations. Search in the forum and found that changing back to 3.0 works and it did. But don't I want to set the target to the latest version to test my app? Or am I misunderstanding something? Thanks Steve Title Comments The topic pretty much says it all. When I changed the deployment target to 5.0, got lots of yellow warnings about deprecations. Search in the forum and found that changing back to 3.0 works and it did. But don't I want to set the target to the latest version to test my app? Or am I misunderstanding something? Thanks Steve

GoNorthWest buzztouch Evangelist Posts: 8197 Reg: Jun 24, 2011 Oro Valley, AZ 1,000,000	01/13/12 05:19 PM (14 years ago) Hi Steve, They are deprecated in the newer versions of iOS, but not deprecated in the older versions of iOS, which is why the warnings go away when you select iOS 3 as a target. Essentially it means you are compiling your app to support a version of iOS where those files are supported. They're still deprecated for iOS 5, but since you also support iOS 3, the warnings go away. And, they are just that...warnings. It means the preferred method is to use other files/methods/classes/etc, as the ones referenced have been replaced or improved. Does that sorta make sense? Mark Comments Hi Steve, They are deprecated in the newer versions of iOS, but not deprecated in the older versions of iOS, which is why the warnings go away when you select iOS 3 as a target. Essentially it means you are compiling your app to support a version of iOS where those files are supported. They're still deprecated for iOS 5, but since you also support iOS 3, the warnings go away. And, they are just that...warnings. It means the preferred method is to use other files/methods/classes/etc, as the ones referenced have been replaced or improved. Does that sorta make sense? Mark

stevek Aspiring developer Posts: 808 Reg: Dec 24, 2011 great neck 8,080	01/13/12 05:30 PM (14 years ago) Mark, I guess so. I guess my next question is why buzztouch creates code that is not fully supported in iOS5 and will that change or does it really not make a difference? If I create an app do I have to say it's only fully supported in IOS3 or can I say IOS5 as long as it builds? Steve Comments Mark, I guess so. I guess my next question is why buzztouch creates code that is not fully supported in iOS5 and will that change or does it really not make a difference? If I create an app do I have to say it's only fully supported in IOS3 or can I say IOS5 as long as it builds? Steve

GoNorthWest buzztouch Evangelist Posts: 8197 Reg: Jun 24, 2011 Oro Valley, AZ 1,000,000	01/13/12 05:39 PM (14 years ago) I'll let BT comment on this if they wish, but generally, if it builds, then it's supported. If it wasn't, I can guarantee you that Apple would reject your app right off. Just because there is deprecated code in some of the files doesn't mean there isn't newer stuff that is supported by the latest OS. And, keep in mind that not all of the new stuff is supported by the older OS versions. So, you want some of that deprecated code in there if you want users with older versions of iOS to be able to use your app. Code gets deprecated and improved all the time. Just because it's deprecated doesn't mean it can't be used...it just means it's generally been replaced by something else. Here's a line from wikipedia that explains it best : <wikipedia> Although deprecated software features remain in the software, their use may raise warning messages recommending alternative practices, and deprecation may indicate that the feature will be removed in the future. Features are deprecated—rather than immediately removed—in order to provide backward compatibility, and give programmers who have used the feature time to bring their code into compliance with the new standard. </wikipedia> Helpful? Mark Comments I'll let BT comment on this if they wish, but generally, if it builds, then it's supported. If it wasn't, I can guarantee you that Apple would reject your app right off. Just because there is deprecated code in some of the files doesn't mean there isn't newer stuff that is supported by the latest OS. And, keep in mind that not all of the new stuff is supported by the older OS versions. So, you want some of that deprecated code in there if you want users with older versions of iOS to be able to use your app. Code gets deprecated and improved all the time. Just because it's deprecated doesn't mean it can't be used...it just means it's generally been replaced by something else. Here's a line from wikipedia that explains it best : <wikipedia> Although deprecated software features remain in the software, their use may raise warning messages recommending alternative practices, and deprecation may indicate that the feature will be removed in the future. Features are deprecated—rather than immediately removed—in order to provide backward compatibility, and give programmers who have used the feature time to bring their code into compliance with the new standard. </wikipedia> Helpful? Mark

stevek Aspiring developer Posts: 808 Reg: Dec 24, 2011 great neck 8,080	01/13/12 05:43 PM (14 years ago) Yes, thanks. Steve Comments Yes, thanks. Steve

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.