We are aware of this issue, which is expected to be fixed in an update this week. Please check back on 3/21.
