Thank you for reporting, this is a known issue and is already fixed in our dev build. We'll make a post when we're ready to share the update
