Why isn't the Windows Build Process for IOS docuemented in a clear mannner?

It’s not a secret. It’s kind of amusing because I was involved in this identical conversation a month ago, from a user like yourself who was not aware that a Mac was necessary to deliver apps for iOS. Honestly, I’m not a developer by trade, but in working to become one, I had to do my due diligence to understand what is required to build apps for Android, and iOS. This research yielded this information.

I’m not a Corona shill. I’m a fan of this SDK and I think it really helps amateur devs become pros. There are some serious problems with Corona, but their lack of transparency isn’t one of them. I’m sure Brent and/or Rob is crafting a PC-response for your inquiry, but let me just tell you, from my personal experience, the fact that a Mac is needed to develop for Apple hardware is not a secret. Corona does say they can help you develop for all platforms, which you can do. The knowledge necessary to accomplish this is something the developer needs to work to attain.

Panc Software is right, you should know that a Mac is required to deliver iOS apps. There is no misrepresentation on Corona’s part.

Jedi,

I’m sorry I disagree about it being a secret.  I looked all over the forums and in the basic tutorials and they led me to believe you could do everything from a windows machine.  I am not implying corona is trying to be devious or underhanded I am trying to alert them to the fact that their is a deficiency in alerting their customer base and future customer base to this issue.  I like corona, the development  team and the opportunity it provides.  That does not belay the fact that this information is missing.

Gooner87 you are wrong.  I am not psychic.  If corona does not document the facts then how am I supposed to just magically know them?  I never suggested Corona was misrepresenting anything.  That is your word.  I SAID they were making it harder to go about this process on a Windows box because they have not documented the entire process.

I’m sorry Panc I keep calling you Jedi… I just realized that’s your title.

Not being able to build iOS on Windows is not a secret or hidden fact.

From the Corona Download Page: https://developer.coronalabs.com/downloads/corona-sdk 

“Please note: Due to Apple’s restrictions, you cannot build for iOS on Windows.”

Also found in the “Install Corona SDK - Windows” guide: http://docs.coronalabs.com/legacy/guide/start/installWin/index.html

“Please note that  Corona SDK on Windows only supports device builds for Android devices. Corona SDK on Mac OS X supports both iOS and Android development.”

Ok… for the third time.  I did not say it was a secret or a hidden fact. I said it was not documented well enough.  The first link you gave Tom was dead.  The second link is for when you first load the product.  That is good.  I wish I had saw it when I was excited and dived right in to start using the product.  Of course here it is several months later and I’m NOW trying a build, its’ been a long time since I read the download sheet so where do I go for build information?

Provisioning and Building — iOS

As I said before that lack of widows build support should be documented in that spot Right at the top since that is going to be the logical spot you are going to go to.

Now I’m being told I basically wasted 99$ to become an apple developer.

Surely if anything it should be Apple that you are complaining to as you’ve managed to buy a developer licence without them making it clear enough that you need OSX? However I’m pretty sure they do make it clear.

Sigh… Glitch please read my previous posts.  No it is not clear or I would not have posted this in the first place.  Everyone here lacks perspective because you have been working with the product forever.  Try to look a this from the perspective of someone new to the product and the build process.  I should not have to DIG for this information. 

The information is clearly posted but I also added a note to the top of the “Provisioning and Building – IOS” so it will be in at least three places.

ok, so it seems like you’re more upset about the fact that you had to do some investigative work on your end before you realized that Apple has a restriction in place saying a Mac is needed to build Apple applications. I guess that’s fair; below is the other thread from another guy who feels the same as you do:

http://forums.coronalabs.com/topic/39138-want-to-hear-a-good-joke/

The thing about both of your cases is, they are the exception that proves the rule. The fact that there aren’t a thousand identical posts would tell us that, the information is transparent to the vast majority of the user base. 

I come from an IT background but had zero knowledge of high-level (lua, java) language and how one would even go about developing software. I did some research, a TON of googling, approximately 2 metric tons of reading (and yes, quite a bit of digging) before I got to the point where I felt half-way competent when dealing with producing something halfway decent. I spent a lot of time developing and testing my app, and released it! But then I found out that, lo and behold, it wasn’t really that fun to play. It was meant for kids, but I fell down in the marketing/sales realm, which has always been and will always be my Achilles heel. 

I didn’t really start this post with the intent of giving my life story, but I wanted to convey the fact that my badge says Pro, I am Jedi level (which really doesn’t mean much) in the forums and I have somewhere between a novice and an advanced amount of knowledge regarding Corona specifically, and Lua in general. Like I said before, Corona does a lot of things poorly. I’d love access to the file directory for Android, I’d LOVE to have Windows Phone/8 support now (I’m impatient) and I would really really like to have a more intelligent way of creating and removing physics bodies without the performance hit (which is more of an issue with Box2D than it is Corona). What they are good at is support. You see Tom just responded and modified their documentation based on your feedback. That’s tough to beat. 

In summation, I think you should take this as the first of many development hurtles you are going to encounter. Use it to familiarize yourself with Apple architecture. Maybe you’ll fall in love with it and want to buy a Macbook and never look back. Maybe you will realize that Android is eating their lunch as far as marketshare and only want to develop for Android. Maybe you’ll realize this whole development thing isn’t for you and you’d rather be a poet or a farmer. You are at the very outset of a journey towards development competence. None of these outcomes are wrong, and we all have been there. 

Panc,

This comment:

“ok, so it seems like you’re more upset about the fact that you had to do some investigative work on your end before you realized”

came off as snide/smug/sarcastic and your assumption is wanting.

I have been working on this project for 2 years with my nephew.  Up until April I would submit my work to him, he would do the build and I would install to my Ipad.  Well Apple’s glorious process just stopped working and I have been unable to install our  APP on my Ipad for testing since April.  Despite not wanting to do it I upgraded to IOS 7 with the hopes that would fix the issue… Nope.

Since waiting for my nephew to build the app always took more time then I cared  for I figured I’d finally buy a Corona Basic license and do builds myself.  I spent little more then _ SOME _ time seeing what needs to be done and after plunking down $300 and wasting hours on trying to get an application on to my Ipad I am in the same spot with no ability to build apps because I do not own a Mac and nor do I have the desire too.

In terms of BIO’s I have been programming since 1978, supporting mainframe and unix systems since 1981 and I have been in CUSTOMER  SERVICE for 8.5 years.  My opening post had everything to do with CUSTOMER SERVICE and making it easy for the CUSTOMER a point with Tom picked up on.

Tom thank you  very much for that update I saw it this morning.  Maybe someone in my similar position will be spared the same pain… that was the ultimate goal of my original post.

If you don’t do your homework or don’t read the relevant parts of the documentation, that doesn’t mean the documentation is not good enough. It’s really your fault.

http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

"Please note that Corona SDK on Windows only supports device
builds for Android. Corona SDK on Mac OS X supports both iOS and Android
development."

I think it’s common sense to read the “Provisioning and Building - iOS” section if you want to build for iOS, before buying anything, so you can see the requirements of the platform.

If you’re definition of transparent is writing in an intrusive way information like that (and other that frustrate people who don’t do their homework) all over the site, then yes. I understand transparency by providing information in the sections of the site that are relevant.

Well Gee beckslash if you had taken the time to read this entire thread then you would have known that that note was added there just yesterday because I started this thread.  Maybe you don’t have as much common sense as you think.  Maybe YOU should try reading first and being less smug. 

Just to chime in…there are 3rd party services available that can build your iOS app for you. As long as you have a cert, http://try.macbuildserver.com/ is one.

As a developer, I have always been aware of the iOS-must-use-Xcode. I’ve been using Apple products since the Apple II and it’s an Apple philosophy to require their hardware to build for it since…forever. It ain’t right, but it is so.

Hi Jack,

Thanks for the that.

I’m all set with actually getting builds out.  My nephew does the builds.  We were just trying to improve the work flow and turn around to builds and not have me waiting on him for builds.

Maybe that post will help someone else who reads this.