Hi Hung,
We were able to reproduce the issue at our end on the iOS device only. So, we are facing some complexities in finding the root cause of the issue because it is either an iOS device compatibility issue or a source level issue. We need some more time to find the root cause of this issue since it is reproduced only in iOS device only. In order to debug further we tried to replicate the reported issue in the Safari browser on a local machine, but we are unable to reproduce the issue at our end.
We are validating this issue with iOS device and will provide further details by December 31, 2021.
Until then we value your patience.
Regards,
Pon selva