@Anonymous
RE: This issue is still ongoing. Our Product Team haven't resolved this unexpected behavior yet but are continuously doing their best for the permanent fix.
Continuously doing their best, for two months? And still haven't been able to figure it out? You know that no one really believes that, right?
