Anyone else getting this error. I have been for a few days now. Thought it was my Internet provider router (it was on the fritz), but I replaced it and still getting the message. It also coincides with trying to upload a new build to a new version of an app already distributed in Apple Connect. I had a few failed attempts for other reasons (like version number not configured correctly) so I thought I may be getting blocked by Apple (as though I was spamming). So, just wondering if it a system (MIT) wide thing possibly. Thanks.
Which server are you using?
Taifun
Hi,
I've been getting the same error "Build failed! Connection refused" while trying to build IOS Ad Hoc (.ipa) on https://iosbuildservertest.appinventor.mit.edu/
for the past two days as well.
Brgds
Thanks Gaber.... I thought it was just me. It had been working nicely actually. Maybe EWPatton can shed some light. Thanks again for replying.
The iOS build functionality has been merged into ai2, so we are no long going to run the separate test server. You should consider migrating your projects to ai2. You can see my note on this here:
(added to FAQ)
I tried importing an .aia file from previous server that worked (meaning I was able to successfully upload to Apple) but when I tried building and uploading using the new server, ai2..., I got this message:
ERROR: Failed to sign framework /var/folders/cj/y0pj22fd5p1g7wk4vrn9gc_80000gp/T/1759375403705_6518026267564097536-0/youngandroidproject/../build/Payload/PlayerApp.app/Frameworks/PSSRedisClient.framework
Aside from importing the .aia file, are there additional steps required to get the build up and running, like a new mobile provision, signing certificate etc? Thanks.
Ok, I was able to successfully upload a new build to Apple from the new ai2 server. For the benefit of others, I could be wrong, but looks like I had to rename the app in Apple Connect to conform to the Bundle IDused in the provisioning profile. Long story, but it seems you can't change the Bundle ID in Apple Connect for an app that has already been reviewed and is in distribution. In my case, I had changed the name of the APP in Apple Connect after the first build was uploaded. Since I was not allowed to upload a new Bundle ID, I reverted the name of the app in Apple Connect back to the name included in the original (and not changeable) Bundle ID. Fortunately Apple Connect allowed this! I then incremented the build in MIT properties and successfully uploaded the build using the original mobile provisioning file. Note: I did not need a new signing signature (which I tried bundling in a new mobile provision thinking that would be necessary with the new MIT server). In fact (as noted above) I was forced to use the original Bundle ID, which had the original signing signature generated from the old MIT test server, and it worked.
So, in summary, I imported the .aia from the old server to the new one. I used the same mobile provisioning file (no new signing certificate), but just had to make sure the name of the app in Apple Connect was (in my case) changed back to match the app name in the mobile provisioning file, which was the project name in MIT (also had to increment the version and build number before uploading). I hope this helps.
-Mark
1 Like