Yes, I was able to reproduce exact behaviour you were seeing when I removed 'true' from the resetContent property. A lot of things breakdown when this is not set, like existing documents not been loaded as expected.
However, I then noticed that in my app I had the property 'preload' set to true. when I removed this property, the application began to behave itself once again. Though now performing less well as now the app is now going back and forth to the server.
These two properties are there to help the mobile app perform better to the user. But they do needs to configured in a certain way. Though maybe the app shouldn't blow up when you don't have these setting precisely set. We'll investigate this.
Thanks for the feedback.
p.