Titanium JIRA Archive
Alloy (ALOY)

[ALOY-482] View-based collection binding not properly clearing children before repopulating

GitHub Issuen/a
TypeBug
PriorityHigh
StatusResolved
ResolutionFixed
Resolution Date2013-01-23T22:14:43.000+0000
Affected Version/sn/a
Fix Version/sAlloy 1.0.0, 2013 Sprint 02
ComponentsRuntime
Labelsn/a
ReporterTony Lukasavage
AssigneeUnknown
Created2013-01-22T22:26:34.000+0000
Updated2018-03-07T22:26:01.000+0000

Description

When running the models/journal test app, I'm getting a series of this warning in the console: 
[DEBUG] [WARN] Called remove for [object container] on [object scroll], but [object container] isn't a child or has already been removed.
[DEBUG] [WARN] Called remove for [object container] on [object scroll], but [object container] isn't a child or has already been removed.
[DEBUG] [WARN] Called remove for [object container] on [object scroll], but [object container] isn't a child or has already been removed.
and in the app the entries are not being cleared after the fetch(), causing lots of duplicates to appear in the scrollview. We need to figure out a reliable way to empty all views from a proxy's view hierarchy.

Comments

  1. Tony Lukasavage 2013-01-23

    The problem has been resolved in models/journal test app for ios by refactoring the add.js controller to only trigger binding once per entry, but a deeper problem still exists in iOS TIMOB that can cause this issue to appear in less scrutinized collection binding code for views. This issue has been logged as TIMOB-12399.

JSON Source