Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The app references non-public selectors in Payload #672

Closed
nielsoo opened this issue Jan 30, 2019 · 13 comments
Closed

The app references non-public selectors in Payload #672

nielsoo opened this issue Jan 30, 2019 · 13 comments

Comments

@nielsoo
Copy link

nielsoo commented Jan 30, 2019

Hi, am I the only one receiving warnings about non-public selectors since a few days when uploading apps to itunesconnect (testflight)? (probably my next app submission will get rejected for this)

this is the warning I get, and these selectors are only used by CocoaAsyncSocket in my project:

The app references non-public selectors in Payload/ newSocketQueueForConnectionFromAddress:onSocket:, socket:didAcceptNewSocket:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:

@zhuyajing001
Copy link

also,the same problem.the question is ,i have to apps.one upload is ok ,the other is The app references non-public .two apps,both use the CocoaAsyncSocket.i whant to knwo why!

@zhuyajing001
Copy link

the app was payloaded,this question does not have effect on app.but why this happed ?

@JensvdHeydt
Copy link

I'm having the same problem with my app. Does anybody have a solution?

@seanm
Copy link
Contributor

seanm commented May 1, 2019

The list @nielsoo gave are all CocoaAsyncSocket methods, not Apple methods. Surely this is just a false positive from whatever Apple is using. Seems you should complain to them.

@github-actions
Copy link

This issue has been marked as stale, it will be closed automatically if there is no further activity.

@fansanelli
Copy link

fansanelli commented Jun 9, 2020

Hello,

I'm experiencing the same issue...
EDIT: I've changed:
newSocketQueueForConnectionFromAddress
INTO
_newSocketQueueForConnectionFromAddress
and the first issue disappeared.
Can someone please investigate?

Many thanks
Cheers
Francesco

@sidhisan
Copy link

Hi all, this issue fixed for me by setting Enable Bitcode as true

@charmingtoad
Copy link

I'm experiencing the same issue. I cannot try enabling bitcode, because a different dependency I'm using was built without it.

Apple's rejection states "If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. "

Even though it is a false positive, Apple asks developers to resolve it by renaming methods that match private Apple APIs.

@Sega-Zero
Copy link

having the same issue on XCode 14 even with bitcode is enabled (which is reasonable: bitcode has been deprecated)

@skam22
Copy link

skam22 commented Sep 14, 2022

same issue here on Xcode 14.

@Sega-Zero
Copy link

the project seems stalled. solved the problem by removing from project

@landonhughes
Copy link

+1 for same issue with Xcode 14

@dishank-betaflux
Copy link

same issue coming

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests