Thank you for your feedback.  I'd patched this issue at our code base but it's not deployed yet.  I think it'll be automatically gone when all codes are at the production deploytment.  :-)  At this moment please ignore it.

Back to normal，Thank you for your prompt reply