I am still seeing the same error after the large update on 2/16. Has anyone heard of a date when they will correct this?
