This should have been caught by the QA team or user acceptance testing as it is a showstopper bug. Let's give them a chance to correct this in a timely manner, though the lead-up to this and the severity/priority of this bug is a pretty glaring issue.
In either case, they have promised unofficially by end of 1/31 for resolution and should be working by 2/1, though it is not in their official communication in the post above. We shall see.
Personally I will give them up to a week or two after their acknowledgment of the issue. If it is still not resolved after this, I will be returning it for a refund and going to their competitors as well.
