It looks like based off their latest update, they have at least now acknowledged it is still an issue: