App rejected due to non-public api's

The message from Apple is self-explanatory, and you mention that you do have a method with the name that Apple thinks may be an attempt to use a non-public API. Renaming them should be all you need. The third-party libraries that you mention are very unlikely to have any non-public API's since they are very commonly used.

..

I have not used it recently, but I have uploaded apps to the app store that used FBConnect. Are you using the latest version of FBConnect. If there are any methods that might trigger app rejection, I would think the FBConnect developers have already remediated it. If not, feel free to send the developers a bug report and have them fix it (you can also fix their code and send them a patch).

I too have a similar problem. The Appstore rejection read as follows:

We found the following non-public API/s in your app:

setViewController:

If you have defined methods in your source code with the same names as the above-mentioned APIs, we suggest altering your method names so that they no longer collide with Apple's private APIs to avoid your application being flagged in future submissions.

I have pressed shift control f and put in setViewController and nothing is found....

Does anyone know where I can start?

Cheers

What third party libraries do you include?

em I'm a bit new to this... Where would I find the answer to that? I have installed the Facebook SDK

Does the Facebook library come with source code? If not, you can manually check with "grep setViewController /path/to/facebook/library"

I dont believe there is a source code just Headers and resource bundles. So i'm not exactly sure what to 'grep'

How will that lead me to the bug?

Does anyone know where I can find the Facebook sdk libraries? Which folder etc so I can feel the setviewcontroller

Cheers

I have the same problem what to do with below points from the apple.

Requires help plz help me my app rejected two times with this points.

We found that your app uses one or more non-public APIs, which is not in compliance with the App Store Review Guidelines. The use of non-public APIs is not permissible because it can lead to a poor user experience should these APIs change.

We found the following non-public API/s in your app:

_tearDown

If you have defined methods in your source code with the same names as the above-mentioned APIs, we suggest altering your method names so that they no longer collide with Apple's private APIs to avoid your application being flagged in future submissions.

Additionally, one or more of the above-mentioned APIs may reside in a static library included with your application. If you do not have access to the library's source, you may be able to search the compiled binary using "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.

We appreciate that you may have made the precautions in your code for using non-public APIs, however, there is no way to accurately or completely predict how an API may be modified and what effects those modifications may have. For this reason, we do not permit the use of non-public APIs in App Store apps.

If there are no alternatives for providing the functionality your app requires, we encourage you to file an enhancement request. Or, try working with the Apple Developer Technical Support team to explore alternative solutions.

On occasion, there may be apps on the App Store that don't appear to be in compliance with the App Store Review Guidelines. We work hard to ensure that the apps on the App Store are in compliance and we try to identify any apps currently on the App Store that may not be. It takes time to identify these occurrences but another app being out of compliance is not a reason for your app to be.

For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to:

- include the complete details of your rejection issues

- prepare any symbolicated crash logs, screenshots, and steps to reproduce the issues for when the DTS engineer follows up.

For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports.

If you have difficulty reproducing this issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Testing Workflow with Xcode's Archive feature".

Stop using private APIs.

What is so hard to understand about that?

But its require to use to send the sms to any number

Well, you can't use private APIs.

You'll have to find an approved way of doing whatever it is you're attempting.

Otherwise, you will never get it in the App Store.

Thanks for you reply.

and also what do you understand by the _tearDown method and this kind of word is never used in my project then how to handle this one.