@alex will transitions fixes be included in the public release?
@GuillermoFG: Thanks for your persistence! The transition bug was a show stopper for me.
@alexf: http://forums.coronalabs.com/topic/44763-why-my-simple-code-leaks/ was also related to the transition bug and have been fixed in 2014.2188. Just tested and no problems anymore. So Bug case 30859 can also be closed. It was a major issue for me so thank you for fixing it!
Super. 2189 is looking real good. Seems like a lot of fixes went into it at the last minute which is wonderful.
Quick question on the storyBoard bug reported by Guillermo. I am glad to see this one fixed as opposed to saying we don’t support storyBoard anymore… Will this also mean a refresh to the storyboard code on the GitHub?
Thank you very much.
@kerem: No storyboard update needed, the issue was not in the storyboard framework, but in the transition framework.
alex
Great news! Thanks for the confirmation.
Hi I have a few bugs to report and they all seems to revolve around repeating patterns on IOS devices. I have a repeating pattern as a background layer and when we try to do things like download images from a server and place them on top they appear black on IOS devices. They work fine on Android and Simulator. Also, if you try and do an effect such as a blur on a layer on top of the repeating background black box appears where the background should be alpha. We are trying to do a glowing text effect in our upcoming game, but these black boxes keep appearing.
We released the new public build today. Go get it!
http://coronalabs.com/blog/2014/03/11/new-public-release-2014-2189/
Great job with the release. I appreciate the fact that a lot of fixes and stability improvement work went in to this release despite all the hush hush new feature work was going on behind the scenes. Thank you very much.
Is there any difference between the public release of 2189 and the daily build of 2189?
Yes. The difference is $588.- :D :D 
Heh, ksan. 
I just meant if we have already downloaded the daily build, is there any need to download the public build or is it the same?
There shouldn’t be any functional differences though there may be binary differences where Starter and Basic accounts are unlocked for the version.
@thegdog, I’m sorry. Just couldn’t pass on the silly joke for the day! Sorry for derailing your excellent question. I too would like to know.
Edit - Thanks Rob. Not downloading the public release then. Already on 2189.
Glad that we are finally close to another public release. Just wish that more widget bugs had gotten addressed. Like mine.
But glad that other users will finally get all the fixes in these recent releases.
Walter, it seems this Daily Build doesn’t address the issue where creating/canceling transitions inside onComplete function of other transitions will trigger a memory leak. I know there is a lot of hard work to do with every Public Release, but, IMHO as Corona SDK is a game engine, an unpolluted transition engine must be essential.
Is there any chance the next Public Release will close this nasty bug?
Thank you and keep the good work!
It would be helpful to post the bug ID of any bugs you are referencing.
Sorry, here is my widget bug:
(Case 30464) scrollView issues: scrollbar jumps, scrollbar cut off at top, scrollBarAutoHide = false does not work reliably
Hi Rob, Regarding transitions:
I filed the bug 29913 about storyboard class triggering enterScene event twice (but not createScene event) I’m pretty sure this is because storyboard uses the transition engine internally for the scenes, and enterScene is in the onComplete function of the transition.
There are some examples of bugs with new transition API in the forum, all of them have in common that are very complicated to reproduce and all of them involves the onComplete param.