It was an issue with 0.32, it's been fixed in 0.33 so you'll just have to wait for that to release publically (probably late april)
