Hm, could've sworn that bug was fixed. We've found that trying a second time usually gets around the issue. Can you try doing so?