Seems like the upgrade to 1.2.1 fixed this issue.