I have had this exact same issue and with a completely clean deployment of 1.2
↧
I have had this exact same issue and with a completely clean deployment of 1.2