Xcode5:The App References Non-Public Selectors in Payload/<Appname>.App/<Appname>: Setattribution:

Xcode5 : The app references non-public selectors in Payload/AppName.app/AppName: setAttribution:

Try downloading the latest SDK version, Facebook says they have addressed this
https://developers.facebook.com/bugs/273730516072926

The app references non-public selectors in Payload/Appname.app/App name: decoder

You may get this warning just for using a selector in your own code or third party code that has the same name as some selector that is marked as non-public. Happens to me all the time. Never got rejected for it.

By "same name" i mean just something as simple as you having an object with this selector:

-(id) XYZKMyClass doSomethingFancy:(id) toThis

...and there being a selector like this for an internal Apple functionality

-(id) ApplesClass  doSomethingFancy:(id) toSomething

So: What it seems they are looking for is the signature -(id) doSomethingFancy:(id). You can see how it's very easy to accidentally bump up against this.

Presumably they perform a deeper check at the App Store Police HQ, and determine that the flagged selector is in your code, and hence OK.

the app references non-public selectors in payload/appname.app/appname: _terminateWithStatus

You can't remove this warning. You may get this warning just for using a selector in your own code or third party code(may be because of facebook sdk) that has the same name as some selector that is marked as non-public. Happens to me all the time. Never got rejected for it. So you won't worry about this warning. See this Ref. , Ref2

And also see this stack question to avoid rejection, find and remove unwanted framework.

non-public selectors operationCompleted:

You may get this warning just for using a selector in your own code or third party code that has the same name as some selector that is marked as non-public. Happens to me all the time. Never got rejected for it.

See this Ref. , Ref2

---

Related Topics