Did you see the follow-up post on the developer’s page?

Sounds like he fixed the issue today.