Multiple Simultaneous Layout Transitions Crash

[victorstewart]

sometimes with nested view hierarchies.... where asynchronous network event driven UI updates might trigger layout changes on more than one group in the hierarchy .... even though transitionLayoutWithAnimation is always called on the main thread, thus the transitions serially requested... i'm seeing crashes saying sometimes like "supernode can't perform layout transition while a subnode is", and the inverse.

i think this is a really dangerous decision to just crash the app in this situation. why can't that transition just be queued up for next?