2014.2368 broke something - could it be something to do with transition.cancel function?

Solar2D Daily Builds and Public Releases
#1

I updated my build from 2014.2354 to 2014.2368 today, and it broke a scene transition (using composer).  The strange thing is, except for this one particular scene, all other scenes that I checked work fine.

Only when I transition from this scene, say, Scene A, to other scenes, it simply hangs.

The terminal output does not give me any error message.  All I know is that it makes it to  phase == “will” of the next scene, but never makes it to  phase == “did”.   The last message on terminal is the last line in the phase == will block (which is a print statement), indicating that the process stopped right there.  Nothing else gets printed on terminal.

When I go back to 2014.2354, all returns to normal, and Scene A transitions to other scenes smoothly without any issue. 

This exact same behavior is observed both on simulator and iOS devices.

Not sure if this is of any help, but I thought it may be worth an alert…

Naomi

Edit:  I looked at the Scene A a bit more, and I do call transition.cancel() immediately before composer.gotoScene function is called.  Perhaps that’s causing the scene to hang?

#2

Yup, this appears to be exactly what Ingemar reported:  

http://forums.coronalabs.com/topic/49376-20142365-composer-did-show-event-not-fired/

#3

Hi Naomi.  Yes, we introduced a regression bug with some recent fixes.  I’d recommend dropping back a couple of daily builds until we can get this resolved. 

Rob

#4

Thank you, Rob.  

I went back to 2014.2354 – I’m almost ready to submit my latest app to Apple.  I thought I’d do the final round of testing with the latest build today before submitting the final release build, but perhaps I should go ahead with 2014.2354 after all (unless you think there are important updates that I should consider and wait for?)

Naomi

#5

I would go with what’s working.  When we fix this bug, there will be fixes for some transition problems that some people are having, but if those are not impacting you now, then you don’t need to wait on that fix.

Rob

#6

Got it.  Thank you, Rob.

Naomi

#7

That’s weird, everybody is seeing that bug with current builds but I’m seeing it with the last public build – I posted about it over here but never got a response:

http://forums.coronalabs.com/topic/49318-how-can-i-stop-the-show-did-phase-from-triggering/?hl=phase

At the time I assumed it was something I’d done – didn’t occur to me it was a Corona bug.

 Jay

#8

Ah, that’s interesting, Jay.

Did you have transition.cancel immediately before the composer.gotoScene?  Or was it something else that caused it for you?

Naomi

#9

Yup, this appears to be exactly what Ingemar reported:  

http://forums.coronalabs.com/topic/49376-20142365-composer-did-show-event-not-fired/

#10

Hi Naomi.  Yes, we introduced a regression bug with some recent fixes.  I’d recommend dropping back a couple of daily builds until we can get this resolved. 

Rob

#11

Thank you, Rob.  

I went back to 2014.2354 – I’m almost ready to submit my latest app to Apple.  I thought I’d do the final round of testing with the latest build today before submitting the final release build, but perhaps I should go ahead with 2014.2354 after all (unless you think there are important updates that I should consider and wait for?)

Naomi

#12

I would go with what’s working.  When we fix this bug, there will be fixes for some transition problems that some people are having, but if those are not impacting you now, then you don’t need to wait on that fix.

Rob

#13

Got it.  Thank you, Rob.

Naomi

#14

That’s weird, everybody is seeing that bug with current builds but I’m seeing it with the last public build – I posted about it over here but never got a response:

http://forums.coronalabs.com/topic/49318-how-can-i-stop-the-show-did-phase-from-triggering/?hl=phase

At the time I assumed it was something I’d done – didn’t occur to me it was a Corona bug.

 Jay

#15

Ah, that’s interesting, Jay.

Did you have transition.cancel immediately before the composer.gotoScene?  Or was it something else that caused it for you?

Naomi