So after the team have been digging through to work out why the app is spitting out errors it turns out that turning off developer mode clears the issue up.

This thing has been spitting out errors since its release in 2012 but the engine was handling it internally 🤣

There are no errors if you can't see them...

*Me boxing the dev*

There's no pain cause you can't see it.

?!

@AtuM We all have feelings...

I really really get angry when logging is either treated like "unnecessary" or not validated / tested.

The amount of time - hence money -, frustration, security implications and so on is staggering when logging is done wrong.

It's a deadly sin.