Same problem here, definitely a bug. Can we please get an official response on this?