@raddevon, @jtreadwell, @Robert_J_Scally: Our investigation so far has revealed that upgrading to the 1.2 caused Insync database corruption for some of the users due to which they have encountered this issue. Could you send across your Insync logs too so that we could confirm? Here is how to find the logs: How to find the log files
If it turns out to be the case for you as well, you will have to resync from scratch as the fix would not be feasible.
We are working on adding additional safeguards to keep it from happening in future.
Apologies for the inconvenience