I fixed this by changing the template, so its not an issue with the plugin – i am very sorry for the inconvenience. I’m going to look further into this as that template is created by the theme and i dont want to get this error again if a theme update changes the template in a way that triggers this behaviour on iOS devices.
