4

I recently upgraded my application from iOS3 to iOS5. And at compile time I have several warnings for using deprecated methods.

Two questions:

1- Will I have problems when run the application in an iPhone with iOS 5?

2- If I did not update the methods, Will Apple accept the application when uploading it to the AppStore?

android iPhone
  • 860
  • 2
  • 11
  • 22
  • 1
    possible duplicate of [Will Apple accept Apps with deprecated code?](http://stackoverflow.com/questions/7909986/will-apple-accept-apps-with-deprecated-code) – Ben Zotto Jan 12 '12 at 19:20

4 Answers4

6

Briefly,

  1. No.
  2. Yes.

See the dupe question for a longer explanation.

Ben Zotto
  • 70,108
  • 23
  • 141
  • 204
6

  1. You will probably not have a problem on iOS 5 devices using methods that the compiler is telling you are deprecated. Of course, it would be a good thing to clear up this issue over time because deprecated means those methods might not be present in iOS 6 (or whatever it will be called).

    • What you need to watch out for are compiler warnings or errors that an object may not respond to a particular method call. These would occur for methods that actually were removed along the way. It sounds like you have already done this, but be sure that you have set your SDK set to iOS 5 in XCode to ensure you are getting all the errors/warnings. But the lesson here is test, test, test (on devices as well).

  2. As long as your code compiles and runs against iOS 5, using a deprecated method alone probably won't get your app disqualified. If it causes any crashing or anything like that during testing, however, they will likely kick it back to you for rework.

aTotalStranger
  • 318
  • 1
  • 9
2

Deprecated doesn't mean removed. Its just a friendly hint for you that these functions might be gone in an future iOS version (eg. 6). Currently they still work and the review team will accept your binary. You should note that the lifetime of deprecated methods in iOS seems to be pretty long, a few methods from NSFileManager are deprecated since iOS 2 (aka iPhone OS 2.0)

However, you are encouraged to update your App at some time, if you have a critical update that needs to be out asap, you can skip this for now, but in the future you have to change your code!

JustSid
  • 25,168
  • 7
  • 79
  • 97
  • 2
    I'll add that the risk of using deprecated methods is less that they'll disappear in the future (they may never disappear) but more that they probably don't get updated over time. So you run the risk of using more dangerous, primitive, less tested functionality over time, which could bite you before the API is actually removed. – Ben Zotto Jan 12 '12 at 19:25
1
  1. Test it. You may not have a problem now but you will likely in the future.
  2. You should be okay (Assuming it actually works) but Apple is fickle. No guarantees.
Dancreek
  • 9,524
  • 1
  • 31
  • 34