Dependency CocoaAsyncSocket Causing ITMS-90338 Appstore Connect Rejections

[RayHughes]

Description:

Dependency CocoaAsyncSocket is causing ITMS-90338 (private api) Appstore Connect rejections. This started occurring today after the iOS 16 keynote. No changes to my build were made and it seems be a wide spread issue affecting many developers & dependencies in cross platform frameworks such as react native.

Note: Some of these API errors are from other dependencies as well. The ones I am referring to are exclusive to CocoaAsyncSocket and socket:: methods.

TMS-90338: Non-public API usage - The app references non-public 
selectors: estimatedProgress, initWithFrame:configuration:, 
initWithURL:configuration:, 
initWithURL:entersReaderIfAvailable:, isMainFrame, 
isPassthrough, navigationType, 
newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, 
removeValuesForKeys:completion:, setNavigationDelegate:, 
setProcessPool:, socket:didAcceptNewSocket:, 


socket:didConnectToHost:port:, socket:didConnectToUrl:, 
socket:didReadData:withTag:, 
socket:didReadPartialDataOfLength:tag:, 
socket:didReceiveTrust:completionHandler:, 
socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, 
socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, 
socketDidCloseReadStream:, socketDidDisconnect:withError:, 
socketDidSecure:, targetFrame, userContentController,** 


websiteDataStore. 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. For further information, visit the 
Technical Support Information at 
http://developer.apple.com/support/technical/

Environment

All

Steps to Reproduce Issue:

1. Archive for Release
2. Upload via Xcode
3. Upload Fails

[RayHughes]

Resolved by Apple
https://developer.apple.com/forums/thread/127678?page=6

[jkasten2]

@RayHughes Thanks for letting us know. Just to callout, OneSignal doesn't use CocoaAsyncSocket but seems like expo does.

[richardReitz]

Same issue on App Store delivery.