IOS SDK - App got rejected because of addBuffer

My App just got rejected after review by Apple:

Performance - 2.5.1
Your app uses or references the following non-public APIs:
addBuffer:

Using Grep in Terminal got the following result:

Davids-MacBook-Pro:cya davidseek$ grep -R 'addBuffer:' *
Binary file Pods/Backendless-ios-SDK/SDK/lib/CommLibiOS/CommLibiOS.a matches
Binary file Pods/Backendless-ios-SDK/SDK/lib/CommLibiOS/libCommLibiOS.a matches

I added the following answer and hope for it to be good enough:

My App got rejected because of "addBuffer". 
This is part of the Backendless-ios-SDK what is mandatory for my App.
Please approve my App since I'm not using "addBuffer", but also have not influence into the Backendless-ios-SDK.
Davids-MacBook-Pro:cya davidseek$ grep -R 'addBuffer:' *
Binary file Pods/Backendless-ios-SDK/SDK/lib/CommLibiOS/CommLibiOS.a matches
Binary file Pods/Backendless-ios-SDK/SDK/lib/CommLibiOS/libCommLibiOS.a matches
Davids-MacBook-Pro:cya davidseek$

I can’t yield on the SDK…

PS: I'm using pod pod 'Backendless-ios-SDK' and there is no update according to "pod update"

Approval issue aside, use pod ‘Backendless’, it is much lighter and does not have all the streaming media code.

What’s wrong with “addBuffer” though? Did they provide any specifics?

Mark

Okay. I’ll use pod Backendless, then. Hope this resolves it.

They did not provided anything. Just complained.

Performance - 2.5.1
Your app uses or references the following non-public APIs:
addBuffer:
The
 use of non-public APIs is not permitted on the App Store because it can
 lead to a poor user experience should these APIs change.
Next Steps
Please
 revise your app to remove any non-public APIs. 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, if you are using 
third party libraries, please update to the most recent version of those
 libraries. If you do not have access to the libraries' source, you may 
be able to search the compiled binary using the "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 tools can help you narrow 
down where the problematic code resides. You could also use the "nm" 
tool to verify if any third-party libraries are calling these APIs.
Resources
For information on the "nm" tool, please see the [url=https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/nm.1.html]"nm tool" Xcode manual page[/url].
If there are no alternatives for providing the functionality your app requires, you may wish to file an [url=https://developer.apple.com/bugreporter/]enhancement request[/url].
If you have difficulty reproducing a reported issue, please try testing the workflow described in [url=https://developer.apple.com/library/ios/qa/qa1764/]Technical Q&A QA1764: How to reproduce bugs reported against App Store submissions[/url].
If you have code-level questions after utilizing the above resources, you may wish to consult with [url=https://developer.apple.com/support/technical/submit/]Apple Developer Technical Support[/url]. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- [url=https://developer.apple.com/library/ios/#technotes/tn2008/tn2151.html]symbolicated crash logs[/url] - if your issue results in a crash log

We have made all private classes as public in binary libs.
You could update the latest Backendless SDK (pod 3.0.39 release) and try again.

I have used “pod Backendless” as suggested and my App got approved earlier today.