This has been reported and we'll take a look. Not sure why this particular release would cause issues, it was working before.