New Public Release: 2014.2381

Flat Corona
Share on Facebook0Share on Google+6Tweet about this on TwitterShare on LinkedIn0

Today we are releasing a new public release of Corona SDK: 2014.2381!

There are a number of new features and fixes in this public release. A great one to note: Composer GUI (in beta) is now available to all users of Corona SDK, including Starter and Basic! Check out the docs and a walk-through.

Also, this build addresses Google Play’s coming deadline around using their advertising ID. Our Admob plugin will work with this release just fine.

Make sure you review the release notes for this public release. They have info on what’s new, important notes and known issues.


Share on Facebook0Share on Google+6Tweet about this on TwitterShare on LinkedIn0

This entry has 30 replies

  1. Lerg says:


  2. MarinK says:

    Nice ๐Ÿ™‚

  3. csr says:

    Thx =)

  4. Fernker says:

    Does this include the ability in the build.settings to skip files? I checked the release notes but couldn’t find mention of it.

    • David says:

      Yes, that is in there.

    • Tom Newman says:

      From the Release Notes:
      All: Added โ€œexcludeFilesโ€ build.settings directive to allow fine-tuning of project -> app file copies. No casenum

  5. Felix says:

    sooo cooool!
    man just in time, thank you soo much…
    I am so curious to include the new admob v2!

    now I just hope that not too much of my old code will be screwed up ๐Ÿ™‚


  6. RS says:

    Just wondering if the Corona particle/emitter features are available to Starter/Basic users with build 2381? Thanks

    • Tom Newman says:

      Sorry no. Particle/emitter APIs are for Pro users and higher.

      • Benny says:

        That’s a real shame. Was really looking forward to this version just because of this. Fine if its not in starter but I think Pro is too high for such a basic functionality of an SDK. You’ve been very generous with other features for free and for basic so why not for particles? $49/month isn’t reasonable just to have access to particles for a hobby developer like me which I thought the basic plan was aimed for. I can’t jump to Pro, basic gives me no extra value so I guess I’ll just stick with starter which doesn’t seem like anyone benefits from at this point ๐Ÿ™

        Please reconsider this choice and I’ll happily upgrade to Basic.

        • Thomas says:

          Hey Benny,

          Too be honest, I don’t think particle emitters should be that hard to program yourself – there’s probably even some Lua code floating around the web for this.

          • Benny says:

            Which is why I don’t understand why this of all features is excluded from users of lower business model tiers when everything else is included.

  7. iFunSoft says:

    How to access features Composer GUI on Starter version (Windows)?

    • J. A. Whye says:

      Composer GUI is only available for Mac at this point.

  8. Just updated. Our entire onCollision postCollision and preCollision events are screwed.. seemes like either masking bits or self.element in our multibody character is not working right. Didn’t see anything mentioned in the release notes about that?

    • Albert Yale says:

      If you provide me with a code snippet (or file a bug with a minimalistic sample) that replicates your problem, I’ll look into it immediately.

      • Andreas says:


        Just an idea:

        I think between the last public build and this one the Box2D engine was updated.

        With the update some problems manifested, small shapes now do not get a physics shape on creation. This might lead to collision events not fired, because there is no physics object anymore that will collide.

        We had a discussion of this here:


        • Albert Yale says:

          Indeed. The rejection of degenerate collision shapes can have unusual side effects. The solution is to make sure that each vertex is unique enough from Box2D’s point of view, possibly growing a shape in the process. This can be a burden for many developers, but we feel it’s worth it, as it allows us to stay current with the latest Box2D developments.

      • We found the issue. It was in the log giving us an error on our physics.addBody for being 1px wide. Made it 2px wide and we are good to go now.

    • Danial says:

      I agree, I have some simple collisions in my game and most of the time the onCollision code is not being triggered. Didn’t have this issue in the earlier public build. ๐Ÿ™ It’s a new app so I can’t release it due to this issue. I’ll try to post something on the forum later on. I have the Basic account.

  9. George says:

    Wow, lots of great updates! Congrats on the new public release.

  10. Arthur says:

    TakeFocus from a scrollview to another doesn’t work anymore, this just destroyed our whole project. What a seriously great update !

    • David says:

      If you post something in the forum giving us more info about what you are seeing, we can see if this is a bug/regression, or if something else is going on.

      And of course, you can also go back to a previous daily build in the very short term.

  11. Nick says:

    Hmm, appears box2d was updated or something going on. Noticing some collision issues with smaller shapes not taking on physics properties. I’ll have to physics objects, but seems like one just ‘forgets’ about the other as doesn’t seem to show up in debug or have any physics properties.

    Just an initial pass on this version, but that’s what i’m seeing and it appears others seem to have that going on to.


  12. Nick says:

    Oh, welllllll here we go, seems to be at it’s core a box2d issue.


    Ok, so it appears you have to mess with it to get it past the minimum threshold, which I don’t know what that is other than build and test and build and test ๐Ÿ™‚

    • kartik says:

      Good to know. Hope this version fixes memory leaks in android phones.

  13. John says:

    Hey, I upgraded to this version, and the facebook.showDialog call on my landscape app uses a portrait webview. So the facebook share dialog is very narrow (and assumed to be tall – off the screen). Any thoughts?

  14. ddi7i4d says:

    Thank you for the update!
    Is Liquid Fun working in Demo Mode or not at all? I would like to know if what I had in mind is actually working before I go Pro.
    At the moment, it appears as it doesn’t work, even the Sample files produce Runtime Errors (except that one with the shapes).

  15. iFunSoft says:

    i need Windows Phone version ๐Ÿ™‚