Walter Luh, CTO, wrote a blog entry regarding our Corona SDK and if the new Apple rules affect you.
Do Apple’s new rules affect you?
Carlos [import]uid: 24 topic_id: 769 reply_id: 300769[/import]
I will not rush for the iPhone. No doubt it will have an owerwhelming success – but not with me…There is yet an additional model of the iPhone coming out. Alright maybe I should say there is an iPhone prototype possibly soon to be the next iPhone4.0. As though our wise phones could not do enough, they’re always looking for a lot more for them to do. The prototype that was found in a bar, that’s right I said a bar, is said to have a camera on the front of the phone as well as within the back. It is said to have a longer battery life, better SIM card, and two microphones! Perhaps soon they will come out with an iPhone that can even babysit for me, since I’m sure that price of the phone is going to equal 6 months day care costs and that’s just when the next model will come out.
[import]uid: 6212 topic_id: 769 reply_id: 1793[/import]
Carlos and Walter,
Do we have an update on the situation yet? I’ve stalled all work until i get some kind of indication where we all stand.
Is your plan to get a confirmation from Apple, or just to continue until there might be a problem? There is a chance for example that nothing will come of this, Apple will just continue approving apps and it was all a ruse to cut out Flash. However that’s not a certainty.
I really appreciate this is tough for you guys, but also for your customers - we need to know where we stand sooner rather than later.
many thanks
paul [import]uid: 5764 topic_id: 769 reply_id: 1796[/import]
We have not heard from Apple. But we have had two apps approved this week and an iPad app update was approved yesterday.
We also have an open dialog with other companies regarding 3.3.1
I strongly believe we are compliant with Apple’s new TOS and 3.3.1
Carlos [import]uid: 24 topic_id: 769 reply_id: 1808[/import]
I am sure that Apple won’t respond and will leave everyone in the dark. That is the risk you gotta take. Actually I don’t see it much as a risk as the Android platform it there as well. [import]uid: 5712 topic_id: 769 reply_id: 1820[/import]
Hi,
I am a new user of Corona. I was checking around, and found this. I am now very concerned about this, because I am learning Corona and I was supposed to start using it as soon as possible for a client project.
The thing is that the new TOS is for 4.0 only and not 3.x, so Apple won’t block anything now based on this because there’re no legal rule they can apply to reject an app that can violate the 3.3.1? Right?
I hope this gets clear soon…
Btw: Thanks for the great work on Corona!
Roberto. [import]uid: 6046 topic_id: 769 reply_id: 2842[/import]
Hi Roberto,
the new TOS is already in affect as it had to be signed by the 22nd of April by current apple subscribers. So if you just signed up at Apple it is already affecting you. And guess what, you won’t find nobody which app got rejected because of it by now. I would not worry. Developing for the IPhone platform was always a risk venture as there is always a chance that apple could reject your app for any reason. Not only for the new rules.
Michael [import]uid: 5712 topic_id: 769 reply_id: 2844[/import]
That’s great, good to hear!
Thanks Michael! [import]uid: 6046 topic_id: 769 reply_id: 2846[/import]
Ok… I just “signed” the new TOS at the developer site…
If this will impact Corona that would be really a bad thing for Ansca and us who want to use Corona!
It seems to be very risky and I am asking myself if I really should gamble on it for more than a “a small app”!
I mean… sure it is risky to develop anything because Apple may reject it… but actually the TOS clearly states that you are not permitted to have an interpreted language for more than a non substantial feature.
First I thought that corona translates a subset of LUA to Objective-C and compiles that… now I know they use an interpreter… I would not blame Apple it they reject corona apps in the future and there will be nothing we can do about that 
Only time will tell… I am definitely not going to invest huge amounts of time into Corona right know… I can easily live with the lost of $99 … but not with the loss of the time investment [import]uid: 6928 topic_id: 769 reply_id: 2911[/import]
First, we don’t use an interpreter. We compile the Lua code.
Second, I’m not sure what version of the TOS you signed, but the newest one is slightly different, in a good way. [import]uid: 54 topic_id: 769 reply_id: 2932[/import]
Can you elaborate on “different, in a good way”?
As I understand it you compile the LUA Source to some kind of bytecode and this is interpreted by your runtime. Right?
[import]uid: 6928 topic_id: 769 reply_id: 2949[/import]
We are under non disclosure, so we can’t comment on specifics in the TOS. The changes should be fairly obvious.
An interpreter allows runtime modifications to the code, through loading or dynamically compiling. Apple prohibits this (and it’s a security hole), and that’s why we don’t do it. [import]uid: 54 topic_id: 769 reply_id: 2953[/import]
. [import]uid: 5712 topic_id: 769 reply_id: 2956[/import]
I just wanted to re-read the TOS I had to sign yesterday but all I find on the developer site is the 3.2 final SDK agreement PDF 
3.2 is pretty clear no problem for corona… what I signed yesterday was pretty obvious a problem
I may have missed the “fairly obvious” change … so as I am a registered developer can you give me a pointer to the text you refer too? [import]uid: 6928 topic_id: 769 reply_id: 2960[/import]
O_O’ Then… The new OS 4.0 TOS from Apple. affect us?
[import]uid: 6934 topic_id: 769 reply_id: 2990[/import]
It looks like using Lua embedded in Object C app should be fine… http://www.appleoutsider.com/2010/06/10/hello-lua/
“Unless otherwise approved by Apple in writing, no interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s). Notwithstanding the foregoing, with Apple’s prior written consent, an Application may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality that are consistent with the intended and advertised purpose of the Application.?”
Cheers
Andrew [import]uid: 3867 topic_id: 769 reply_id: 3031[/import]
Well… to cite the text you posted:
- “… with Apple’s prior written consent an Application may use …”
… would mean trouble because we do not (yet?) have prior written consent to use it.
- “… for providing minor features or functionality …”
… nor we have “minor features” in lua…
If later would be true our whole programming where for implementing minor features… which is obviously a wrong interpretation of what I am doing right now when using Corona.
The whole wording could as well be used to lock us out because we need to get prior written permission and we won’t ask for it… won’t we?
It could also mean that we are no target because even if our game logic is in Lua… there is a lot of other stuff in the app… which technically is similar to other developers systems which also use Lua for their apps.
But it is less restrictive and frightening than before I guess… hmm… is it? [import]uid: 6928 topic_id: 769 reply_id: 3032[/import]
I’ve been keeping an eye on this as whilst i’ve bought corona i’ve held off until i feel happy one way or the other. The new TOS (i believe it’s new, for iOS 4) talks about written consent. So i guess there is a chance that ansca might be able to get something that would put fears to rest once and for all. There is still the old clause about developing in objective c or javascript and *technically* corona fails that even if i gets converted into objective c.
Does the written consent sound like a possibility?
Certainly watching from the sideline for a while the new versions of corona are looking very nice indeed
cheers
paul [import]uid: 5764 topic_id: 769 reply_id: 3033[/import]
The interpretation of what a developer does with Corona depends on vantage point. Look at the big picture: the Corona engine has several person-years worth of work in it. So if someone spends a month working on an app, say, then from Apple’s perspective the Lua code would be less than 3%. This is not to downplay your effort in any way, but you’re actually not adding any new features to Corona, just repurposing what is already there, and adding “minor” functionality. To you it may feel major, and it is, but from a percent of binary size or lines of code standpoint…
[import]uid: 54 topic_id: 769 reply_id: 3037[/import]
Well you can interpret it that way… as I already said in the end of my previous post. All cool if it helps 
So all we need is that you get the written permission to allow yourself and hopefully your customers to use your framework by implementing minor features and functionality in Lua for creating iPhone applications, please!
Or do we need to ask Apple about using Lua as part of our application whe “cough” wrote and compiled in Objective-C?
What’s next?
I bet it is going back to wait till Apple will reject the first Corona App because of violation against this part of the TOS [import]uid: 6928 topic_id: 769 reply_id: 3043[/import]