Looks like the team was able to track this issue down and get a fix in for it.
It wasn't ready to go for our update on May 1st, but should go out sometime next week.
Our apologies for the inconvenience with this bug.
Looks like the team was able to track this issue down and get a fix in for it.
It wasn't ready to go for our update on May 1st, but should go out sometime next week.
Our apologies for the inconvenience with this bug.
Bookmarks