Still not quite sure, what was causing the error, but updating the source code to 4.18.3 seems to have fixed it.