Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
Sencha Premium Member
I noticed that the Ext.Container.setActiveItem no longer accepts a component id. This is easily overcome by calling Ext.getCmp or getComponent on a container but that was a pretty convenient feature. Just commenting on its absence.
thanks again for such fantastic work
This sounds like a bug. I'm going to move this over to the bug forum.