We’ve just merged a patch that addresses that particular problem (it should be resolved for all Oneboxes):