Info Sharing : Error in Function 565 & 221

Solar2D Widgets
#1

Hi guys,

Just wanted to share my findings.  Hope it helps someone.

My composer page has nested scroll views (scroll view within a scroll view). These scroll views has multiple ‘containers’ inside it.

Crash Error Details on windows Simulator :

?:0 attempt to index field 'parent' (a nil value) stack traceback: ?: in function \<?:565\> ?: in function \<?:221\>

To solve this, you need to remove each inner-individual scrollView before removing (display.remove) the outer scroll view (or other display-parents it is inside).

I only notice this issue in build 2015.2638 and not in 2015.2545. Release notes between these builds pointed out some changes in the container, which I have no time to really drill in.

#2

Took me forever to find out this bug (consequences appeared after the next gotoscene)… Thanks for your help @yosu !

(I was working on 2649 but I’ll fallback on 2552, before all those bugged scrollview builds started to pop)

#3

Can someone file a bug report on this please?  Make sure you submit a .zip file (not a .rar file or any other format) that contains the use case that’s causing this bug.  It needs to have a build.settings and config.lua and any assets needed to run.  Engineering can’t make up things for you or we will never find your problem.  Use the “Report a Bug” link at the top.  It’s helpful to paste the URL of this post in the bug submission as well as when you get the confirmation email, post the Case ID # back here as a reference.

Thanks

Rob

#4

Took me forever to find out this bug (consequences appeared after the next gotoscene)… Thanks for your help @yosu !

(I was working on 2649 but I’ll fallback on 2552, before all those bugged scrollview builds started to pop)

#5

Can someone file a bug report on this please?  Make sure you submit a .zip file (not a .rar file or any other format) that contains the use case that’s causing this bug.  It needs to have a build.settings and config.lua and any assets needed to run.  Engineering can’t make up things for you or we will never find your problem.  Use the “Report a Bug” link at the top.  It’s helpful to paste the URL of this post in the bug submission as well as when you get the confirmation email, post the Case ID # back here as a reference.

Thanks

Rob