Hi @fernadnoomgf, the function manageRowLifeCycle only exists in tableView code, not scrollView so I’m a bit confused about how you can be getting this messages if you’re only using a scrollView. Or are you getting a different error that related to contentHeight? If so can you post the whole stack trace for that?
Thanks
Rob
Same error same daily build ios7. I am not using Storyboard or scroll table views and where the crash happens there are no widgets anyway (both in the entering and leaving scene). Error started when using Chartboost and Vungle. I suspect Chartboost. You need to fix this. I cannot provide code, the error is erratic and is not happening on my code (which is why I suspect the ads SDKs). Using iOS7 workaround for landscape app. Seriously, fix this, if I take off chartboost, vungle crashes on landscape apps and sponsor pay does not bother activating my account, then I might as well do something else with my time.
If you feel these are errors, with a particular plugin, you need to post a message in the appropriate forum as the vendors handle support of their individual plugins. They build, maintain, and support their own.
The error in the OP is clearly coming from our tableView widget. Now I don’t know if the vendors are using our tableView’s or not. As far as Vungle goes, I just submitted an app of mine using Vungle that is landscape and I wasn’t having issues.
Thanks
Rob
Hello,
Are there any news about this error?
thanks.
@farandsoft, no, I have reverted back to build second to last before G 2.0 (i.e. 1xxx). Now I am porting project in 2.0 but will take me some time to figure out if under the new engine the error repeats. I am tempted to go for a custom Enterprise plugin for ad networks regardless.
I have resolved my problem, I have a tableview inside scrollview and the error occurred when later to destroy scene, we returned on it. The solution has been to add “removeSelf” to the list on destroyScene.
Maybe it’s a newbie error!
Thanks.
I just went to 1260 from 1183 and have this problem, too. I can repro it at will in my app by creating a pickerWheel, removing the pickerwheel, and then doing a suspend/resume. On resume, I get an endless loop (!) of the _manageRowLifeCycle error.
1260 is dated 11/13/13. This commit is also dated with that same date, and includes a change to deal with a suspend/resume event handler:
https://github.com/coronalabs/framework-widget/commit/572a3b5a8edd7bc14bdb0ea385039abd8bbd88fc
So, is that commit the cause of the bug and is in 1260, the fix for the bug and is in the first Graphics 2.0 build, or extremely coincidental but irrelevant?
Confirmed, btw, that the problem is not in 1259. Rolled back to that until going to a v1 compatibility build – 1260 is a no-go.
Hello,
Are there any news about this error?
thanks.
@farandsoft, no, I have reverted back to build second to last before G 2.0 (i.e. 1xxx). Now I am porting project in 2.0 but will take me some time to figure out if under the new engine the error repeats. I am tempted to go for a custom Enterprise plugin for ad networks regardless.
I have resolved my problem, I have a tableview inside scrollview and the error occurred when later to destroy scene, we returned on it. The solution has been to add “removeSelf” to the list on destroyScene.
Maybe it’s a newbie error!
Thanks.
I just went to 1260 from 1183 and have this problem, too. I can repro it at will in my app by creating a pickerWheel, removing the pickerwheel, and then doing a suspend/resume. On resume, I get an endless loop (!) of the _manageRowLifeCycle error.
1260 is dated 11/13/13. This commit is also dated with that same date, and includes a change to deal with a suspend/resume event handler:
https://github.com/coronalabs/framework-widget/commit/572a3b5a8edd7bc14bdb0ea385039abd8bbd88fc
So, is that commit the cause of the bug and is in 1260, the fix for the bug and is in the first Graphics 2.0 build, or extremely coincidental but irrelevant?
Confirmed, btw, that the problem is not in 1259. Rolled back to that until going to a v1 compatibility build – 1260 is a no-go.
I get this on 2160 also if the a storyboardoverlay has a widget.newPickerWheel in it, when the scen destroys and I got back to the main screen, lots of these errors. Only happens if the pickerwheel has been created
I have this problem too. This is a real problem because building with 1259 isn’t optimized for iOS7, so Apple may reject builds using 1259. Can we get this fixed?
I get this on 2160 also if the a storyboardoverlay has a widget.newPickerWheel in it, when the scen destroys and I got back to the main screen, lots of these errors. Only happens if the pickerwheel has been created
I have this problem too. This is a real problem because building with 1259 isn’t optimized for iOS7, so Apple may reject builds using 1259. Can we get this fixed?
I am having this issue as well. There’s no option for me to switch to a different build (need support for iOS7 and still a working Graphics 1.0). Is there a solution?
You should be able to get the open source version of the widget library from github and use it to get past this issue.
You are probably not going to be able to deploy to iOS using 1260 any longer because of Apple’s new restrictions on the IDFA (Identifier For Advertisers). This was baked into the Corona Core prior to build 2169, where we removed it and pulled the Facebook SDK out into a plugin.
Unless you are using advertising in your app, it’s very likely to be rejected by Apple.
Rob
Hi Rob,
Thanks for the info. I have been rigorous and removed the widget altogether. 
The app I’ve been working on has already got a huge code base and dates from 2011. It originally was created with a very very old version of CL and I have been able to gradually update to build 2162. But I foresee massive rework if I ever need to upgrade it to later builds and using graphics 2.0. Anyway, it is working now so let´s try to get it on the app store.
Best regards,
`Rob
I am having this issue as well. There’s no option for me to switch to a different build (need support for iOS7 and still a working Graphics 1.0). Is there a solution?
You should be able to get the open source version of the widget library from github and use it to get past this issue.
You are probably not going to be able to deploy to iOS using 1260 any longer because of Apple’s new restrictions on the IDFA (Identifier For Advertisers). This was baked into the Corona Core prior to build 2169, where we removed it and pulled the Facebook SDK out into a plugin.
Unless you are using advertising in your app, it’s very likely to be rejected by Apple.
Rob