The 2/24 update apparently did not fix the error. They are reportedly trying to fix this for the next update.
