Indeed, based on the feedback I’ve received, this issue does occur on certain devices when using the mobile version. However, I haven’t identified the cause yet. I’ll address it as soon as possible.