Ahoy hoy, this is fixed in our next update, and I just added it to the Known Issues blog. Thanks, all!