If you’re using client credentials, we had someone last month where it worked on his wife’s Mac, but it wouldn’t work on his. He couldn’t even deploy Xcode built apps either. He could use his cred’s, but not his clients.
There is way too much magic there that most people don’t know what’s all going on.
This problem keeps on persisting for more than 5hours now
I can build just fine. Network routing issue, perhaps?
Is this still an issue?
Has just started happening to me too with exactly the same error info.
2015-02-21 09:28:38.535 Corona Simulator[27888:81516] WebServices: Call corona.build.6 failed in 1424474918 seconds: /CFStreamFault
2015-02-21 09:28:38.535 Corona Simulator[27888:81516] response: {
“/FaultCode” = “-65794”;
“/FaultExtra” = {
domain = 1;
error = 60;
msg = “Stream Error”;
};
“/FaultString” = “/CFStreamFault”;
“/kWSResultIsFault” = 1;
}
Just tried an Android build of the same app - worked fine. So tried IOS again - but same error.
I just did an iOS build with no problems. Are you using any plugins?
Rob
Thanks for the quick reply. I’ve managed to do another IOS build ok. Suspect I have a certificate issue - going to try recreating the Code Signing Identity.
I’m beginning to really lose it! I have deleted both the App ID and the Provisioning Profile and recreated both of them, carefully comparing to the ones that work. Still the same result!
This does not sound like a certificate/profile issue. Are you using plugins? Have you tried building a sample app like “Hello World” yet?
Rob
FYI I just tried and was able to build an iOS app.
No it doesn’t sound like a cert issue.
I’ve been successfully using Corona for months now.
The full picture in this case: I have a single app which converts to a demo version by a single line of code “demo=true/false”
I have created app IDs and profiles for both versions. The full version builds with no issue. The demo version (one word change in the code) and a different Code Signing Identity and the above error occurs.
The only funny is that when I first built the demo (over a month ago) I mistakenly used my own web address rather than my clients in the Apple ID.
In desperation I have just rebooted my Mac and am about to try again.
and the Android build of the demo works fine.
Not surprisingly, the reboot didn’t help. I really don’t know where to go next!
I’ve just noticed that the error message is now more verbose:
2015-02-21 12:07:28.487 Corona Simulator[793:15343] WebServices: Call corona.build.6 failed in 1424484448 seconds: /CFStreamFault
2015-02-21 12:07:28.487 Corona Simulator[793:15343] response: {
“/FaultCode” = “-65794”;
“/FaultExtra” = {
domain = “-1”;
error = “-65795”;
msg = “The server did not return a ‘text/xml’ response.”;
};
“/FaultString” = “/CFStreamFault”;
“/WSDebugInHeaders” = {
Connection = close;
“Content-Type” = “application/x-httpd-fastphp”;
Date = “Sat, 21 Feb 2015 02:05:39 GMT”;
Server = Apache;
};
“/kWSHTTPResponseMessage” = “<CFHTTPMessageRef 0x7f8a0483d800(0x7f8a0483d810)> { parsed response, url = https://developer.coronalabs.com/services/xmlrpc, status = 200 }”;
“/kWSResultIsFault” = 1;
}
What is different with the code signing?
I have narrowed it down to this. When I create the signing stuff with my client’s apple id the problem occurs. With my own it diesn’t. It used to work ok. I’m not sure if the change is because of my recent Corona upgrade or Apple playing around with their stuff to accomodate TestFlight.
All,
I had a similar problem about a month back. I installed some client certificates on my machine to build their app and then all holy heck broke loose.
After spending a lot of time trying to clean up and remove certificates, I finally threw in the towel and rebuilt my mac. This should not have been necessary, but I couldn’t find all the places certificates were being cached and ‘remembered’ between: keychain, xcode, and Corona.
Long story short, if you can survive a rebuild … at least you’ll have a freshly built machine. :\
Thanks Jedi, Good to know that I’m not rowing upstream alone. Let’s hope Rob can come up with a better solution than a rebuild.
Well I don’t know what changed overnight (Oz time) other than my brain being refreshed by sleep but I’ve just gone through the whole process again - new app id, new profile, new iTunes Connect entry, new Corona build and it all worked perfectly!
And I must say a big thank you to Corona for tidying up the Code Signing drop down.
Thanks Rob for sticking with me - I’ve used many of your posts in the past - I’m mightily impressed by the way you work so hard to help people. Keep up the good work.
Peter
PS Of course I’m now stuck with entries at iTunes Connect that I can’t delete - don’t you just love Apple? Such wisdom! But I have learnt : never delete an App ID!