Yep, SE stated that this was solved on March 5th, but i still get the same error