Update: The problem should now be resolved. Watch apps should upload as normal once again.
Developers are flocking to Apple’s developer forums today as the iTunes Connect submissions process is currently experiencing a glitch which makes it impossible for developers to submit apps that include Apple Watch extensions.
Rather than continuing submission process as normal, the system is incorrectly flagging up misuse of an Apple private framework called SockPuppetGizmo. Naturally, this is causing frustration in the developer community at the moment because it prevents apps from being submitted to the App Store.
Before apps reach human approval, they are first sent through an automatic process to verify certain elements of the submitted code usually checking for private API usage and such. It is this step where the bug resides causing erroneous rejections.
Internally, the SockPuppetGizmo framework handles much of the cross-device communication between the iPhone and WatchKit apps. The submission system is incorrectly reporting that developers are linking to non-public libraries and therefore rejecting the binary.
Although this framework is technically private, developers are doing nothing wrong and even old apps are now being rejected which were once approved, confirming it is a bug on Apple’s servers. The screenshot above shows an unchanged binary failing validation today that was successfully submitted to the App Store in late April.
There is no known workaround so right now there is no way to get around the problem. Developers wanting to submit apps that include Apple Watch apps are simply unable to do so currently.
Although this is annoying for the time being, Apple will likely fix the problem soon so developers can continue going about their business as normal. Apple is yet to comment on the matter, however.
FTC: We use income earning auto affiliate links. More.
I don’t even have a Watch extension in my app, but I also saw problems with submitting my app last night. In fact, Xcode would crash every time I tried to do so. I never got any error messages like are being shown above.
I can confirm that as well. Even though this can be solved by closing all xCode windows but not the Organizer one. Then submission should work, but you are getting instantly the automated message that you are using private APIs as described in above article :-(
I’ll have to try that. As I said, I got no errors before. I ended up just using Application Loader to submit the beta build of my app. As for private APIs, the only changes I made were in the storyboard. I guess that’s a no-no now. Whatever is broken sounds like it’s a huge deal, so I’m sure Apple will fix that ASAP.
But we’ll have to wait 7 days for the fix to be approved.
Do agree Josh, the 7 days are a no brainer too. Seems Apple is always waiting until the 7th day after release ;-)
APPLE IS DOOMED
Thanks for confirming, drove me almost nuts in the past 2 hours ;-)
Seems to be up and running again. At least I didn’t get the nasty email again, and my binary did show up in itunesconnect.
Stay strong Whatsapp developers, it’s going to be fixed soon