All geek questions in one place

Use obsolete methods in iOS 5

I recently upgraded my application from iOS3 to iOS5. And at compile time, I have a few warnings about using deprecated methods.

Two questions:

1 Will I have problems launching the application on iPhone with iOS 5?

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

+4
source share
4 answers

  • You probably won't have problems with iOS 5 devices using the methods that the compiler tells you are out of date. Of course, it would be nice to clarify this issue over time, because obsolete means that these methods may not be available in iOS 6 (or whatever it is called).

    • You should pay attention to warnings or compiler errors that the object may not respond to a particular method call. This will happen for methods that were actually deleted along the way. It sounds like you've already done this, but make sure you have installed the SDK in iOS 5 in Xcode to make sure that you get all errors / warnings. But the lesson here is test, test, test (also on devices).

  • As long as your code compiles and works against iOS 5, using only an outdated method will probably not disqualify your application. However, if it causes any kind of failure or something like that during testing, they will most likely push it to you for revision.

+6
source

In short

  • No.
  • Yes.

See the bug question for a more detailed explanation.

+6
source

Outdated does not mean removal. This is just a friendly hint that these features may disappear in a future version of iOS (e.g. 6). They are still working now, and the validation team will accept your binary. You should note that the lifetime of obsolete methods in iOS seems rather long, several methods from NSFileManager are deprecated since iOS 2 (aka iPhone OS 2.0)

However, you are invited to update your application at some time, if you have a critical update, which should be as soon as possible, you can skip this now, but in the future you will have to change your code!

+2
source
  • Check this. You may not have a problem now, but you are most likely in the future.
  • You should be fine (suppose this really works), but Apple is fickle. There is no guarantee.
+1
source

Source: https://habr.com/ru/post/1390706/

More articles:


All Articles