Sorry for late reply. The improvements were made on February 4, but released a bit later than you encountered the problem. If you try again, the problem should not occur.