The problem was resolved in the 215.0-rc1 Client software that we released today. Thank you for reporting this issue.