-
Notifications
You must be signed in to change notification settings - Fork 2k
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
App store rejection #226
Comments
Hmm, I haven't noticed this, and I've been submitting apps with SocketRocket pretty recently. I'll keep an eye on this. |
Same issue here. Please mark #228 as a duplicate. |
I am also getting this error while submitting app. I was previously using test flight, but that went away last week so as people transfer to iTunes connect deployment, I imagine this issue will become very present... |
+1 app store rejection on TestFlight here. |
As a general rule, it's probably just best to avoid prefixing method names with underscores: "Don’t use the underscore character as a prefix for your private methods. Apple reserves this convention." (Apple/Coding Guidelines/Naming Methods) |
@dillonykyang Does this affect any specific versions of SocketRocket? I just had an app accepted which is using SocketRocket version 0.2.0. |
I just had a look at the source for the old 0.2.0 version which I am using, and @acorscadden please could you check which version SocketRocket you were using, thanks! Apple are being petty here, but it's just a private method, and if a rename is all that is needed, then let's do that. It can just be called |
…ect / disconnect
I created a PR. |
fix facebookincubator#226: rename _connect / _disconnect pair to connect / disconnect
Hi! Everyone, we got successfully deploy a new app with socketRocket Blumr for android, ios and web. |
Running into this issue trying to upload our build to iTunes Connect today. Apple complains we are using non-public APIs. |
Fixing this with #252. Thanks for bringing this to our attention! |
The use of _connect method in SRWebSocket.m is causing the app being rejected in the automated screening process during an app store submission.
Here's a reply from the Apple review team.
The text was updated successfully, but these errors were encountered: