From The Blog: Apple now requires Xcode 8.3.2 for submitted apps

Getting Started Announcements
#1

As of Wednesday, May 10, 2017, Apple will require all submissions to iTunes Connect be made with Xcode 8.3.2. This has two impacts:

  1. You must install Xcode 8.3.2 and begin using it immediately for submissions.
  2. Corona Labs has updated our build servers, enabling Xcode 8.3.2 for the latest public release ( 2017.3068 ).

If you are using the latest Corona public release, you only need to update Xcode. If you are using a more recent daily build, you’ll need to update your version of Corona to 2017.3078 or later.

View the full article

#2

I noticed today when I submitted my build that I didn’t get the warning. Good job.

#3

Well that’s just great!

Xcode 8.3.2 isn’t supported on El Capitan (10.11.6) and my Mac cannot be upgraded to Sierra.

Time for a new Mac by the look of it.

#4

I hate to hear that @robin.jones. Were you able to run Xcode 8.3? It seems that Xcode 8.x has always required macOS 10.12. 

Rob

#5

Is this required for building and submitting to itunes or just the submitting part? What about Application Loader? I too own a mac that doesn’t support Sierra. The latest xcode available to me is 8.2.1.

#6

The apps are built with Xcode 8.3.2 on Corona’s build servers.

I’m not sure what will happen if you use another version when you submit.

#7

I don’t think submit matters, as long as Corona can sign your app.

#8

In that case I’m a little confused as to how builds for ios are created (for Corona SDK, not Enterprise).

  1.  I thought that the build was completed on my own machine using my version of xcode.
     
  2. I thought that the version of xcode directly correlates to the minimum iOS you can target. So if you are forced to build using the latest xcode doesn’t that mean you can’t target anything less than iOS 10.x?
#9

When you build, we compile the code locally and the bytecode is sent to our server for packaging and signing. The signed files are sent back and packaged locally and you get a resulting .app, or .iap depending on your post-build choice.

The version of Xcode and the iOS SDK are important through our build process and it’s important when it gets back to package everything and code sign it.

Rob

#10

this sucks… so no choice for everyone to upgrade to os sierra. Typical BS from a silicon valley tech company rotten to the core.

#11

I’m in the same boat here. DOSDude has a Sierra patch that may allow some iMacs to go to Sierra. Seems ok, but not working for me Otherwise, I’m not sure what I will do. With the freemium market being what it is already thinking of throwing in the towel What about Mac In The cloud? Is that viable for just build and submit?

#12

Quite a few people use Macincloud, but other will pick up a Mac Mini and you can probably find one used for not too much. I’m using a 13" MacBook Pro that’s a mid-2012 model. I’ve put in the max memory (16 gb) and I took out the DVD drive and the hard drive that came with it and now have a 512GB SSD as the boot drive and a 2TB HHD to hold projects, music, photos, videos etc. Between the speed of the SSD and the extra memory this 2012 i5 Dual Core processor is a good machine and it can run the latest macOS.  Now of course there will come a time where I can’t upgrade, but I think I have a few years left in this computer.

Note, tricking out a MBP will void your warranty and modern one’s can’t be upgraded. 

Rob

#13

I bought a cheap MacBook Pro from ebay. (Mid 2010). Upgraded the memory to max 8 gig. Works fine for Corona and for uploading binaries. The simulator will not run but I don’t use it. Rather run live builds. And it runs Sierra just fine.

#14

@Rob

Since iOS builds are partially built on Corona’s servers, would it be possible for Corona to offer a service where the entire build happens on your servers? As far as I know, services like MacInCloud are super slow and cumbersome to use.

This is something that I would pay money for, though I’m not sure how much. Maybe $99 for unlimited builds for a year?

I think it would be a useful service for developers who don’t own Macs and for those of us who own out-of-date Macs.

#15

That would require us to transfer all your assets to our servers and send back the complete .app file. While I have a fiber connection at home, the speed wouldn’t be a problem for me, but many of you might only have a 1.5mbit upload speed or less and I think you would find that a bad experience.

Rob

#16

I noticed today when I submitted my build that I didn’t get the warning. Good job.

#17

Well that’s just great!

Xcode 8.3.2 isn’t supported on El Capitan (10.11.6) and my Mac cannot be upgraded to Sierra.

Time for a new Mac by the look of it.

#18

I hate to hear that @robin.jones. Were you able to run Xcode 8.3? It seems that Xcode 8.x has always required macOS 10.12. 

Rob

#19

Is this required for building and submitting to itunes or just the submitting part? What about Application Loader? I too own a mac that doesn’t support Sierra. The latest xcode available to me is 8.2.1.

#20

The apps are built with Xcode 8.3.2 on Corona’s build servers.

I’m not sure what will happen if you use another version when you submit.