Strange stack trace at the end of enterScene... How can I troubleshoot further?

Solar2D Composer
#1

I am in the process of moving my app to #2076. A certain storyBoard screen is giving me the following once enterScene completes executing. I used Glider debug to check line by line and verified that enterScene runs fine. Right after the last line executes the following error pops up. 

I did not get this in earlier G1 builds so I’m thinking its somehow related to the new G2 build and therefore must be a bug of somesort. I don’t know how to pin it down further though. Any ideas?

Thanks

?:0: attempt to perform arithmetic on field ‘x’ (a nil value)

message

stack traceback:

    ?: in function <?:218>

    [C]: ?

    ?: in function ‘_listener’

    ?: in function <?:141>

    ?: in function <?:218>

#2

Would really need to see the code, ksan…I mean, it’s trying to do some kind of math using an .x value. Usually this means some object in the scene (or the scene itself) is undergoing an xPos calculation but the object holding it doesn’t use .x.

Could be changed storyboard timing, could be an object that had .x but doesn’t now…lots of possibilities…

#3

Yup. I reckon it will turn out to be something like that. I am still in the process of converting all colors to /255 notation and getting rid of all depreciated API calls etc so it can be a one of those things lurking in there somewhere. I’ll post an update once I’m confident there is nothing in there that I’m aware of that might cause this. Or maybe the next daily will fix it who knows… 

#4

Would really need to see the code, ksan…I mean, it’s trying to do some kind of math using an .x value. Usually this means some object in the scene (or the scene itself) is undergoing an xPos calculation but the object holding it doesn’t use .x.

Could be changed storyboard timing, could be an object that had .x but doesn’t now…lots of possibilities…

#5

Yup. I reckon it will turn out to be something like that. I am still in the process of converting all colors to /255 notation and getting rid of all depreciated API calls etc so it can be a one of those things lurking in there somewhere. I’ll post an update once I’m confident there is nothing in there that I’m aware of that might cause this. Or maybe the next daily will fix it who knows…