Whenever you are informed of a deprecated method, search the documentation for that method and see what it tells you. In this particular case, I didn't find the deprecated notice for this one, but did find these methods:
stringWithContentsOfFile:encoding:error:
stringWithContentsOfFile:usedEncoding:error:
For the first one, the documentation states: If the file can’t be opened or there is an encoding error, returns nil.
There is nothing about a warning that will automatically stop you from submitting to the store. HOWEVER, there are a variety of reasons that you should address all warnings and errors before submitting your app, including:
1) Warning indicates that you are using a private method, which these days is a cause for rejection
2) Warning indicates an incorrect method name, which will crash if that portion of code is run
3) Deprecated warning should work right now, but may stop working at some point in the future. We don't yet know how aggressive Apple will be with removing stuff from the iPhone OS.
There are a variety of harmless warnings, too, but in general, fix them all.
|
