This still happens for me with 1.3.2 after a factory reset. If you haven't already, I would suggest opening a ticket with support.