Yea sorry for this, a very recent required SDK update caused this, I already have a patch in the pipes though, expect a fix very soon!