Creeland opened this issue 3 years ago · 0 comments
The issue seems to primarily be affecting Chrome users on IOS. I attempted to reproduce the issue which resulted in this error message.
