This is an issue that has been identified, and is expected to be fixed in an update this week. Check back on 3/21.
