I don’t know what specifically caused this, but updating to 5.4 stopped the error from popping up.
1 Like
I don’t know what specifically caused this, but updating to 5.4 stopped the error from popping up.