[Updated Jan. 29]
Although this issue was supposed to be fixed during the maintenance on January 29th, our team encountered additional problems that led to further complications. Hence, we are still working to fix this issue.
Based on our progress, we are expecting the fix to be implemented during the scheduled maintenance in February. We sincerely apologize for the inconvenience.
===
We are planning to fix this issue via the update on January 29th.
Although this issue was supposed to be fixed during the maintenance on January 29th, our team encountered additional problems that led to further complications. Hence, we are still working to fix this issue.
Based on our progress, we are expecting the fix to be implemented during the scheduled maintenance in February. We sincerely apologize for the inconvenience.
===
We are planning to fix this issue via the update on January 29th.
===
We have been receiving reports from our users regarding this issue.
If there are any new infomation regarding this matter, we will post them in this FAQ and/or other venues.
Thank you very much for your cooperation.