In other posts I've read, I see this was supposed to be fixed and updated today (2/20), but even though I updated it, I'm still having the same issue. So, no, it was not fixed <sigh>.
