Sorry to send you on a wild goose chase! >
No worries. It's good to explore all avenues. > And now I don't understand what's going on with that database. :( > Me neither. Maybe because I use putExistingRevision heavily? And perhaps the revision histories are getting messed up causing this problem? I thought about just creating new revisions when syncing instead of using putExistingRevision, but I didn't know how to avoid a sync loop. And in this case, by syncing, I'm referring to my CloudKit sync implementation, not the native CBL syncing. I use putExistingRevision to facilitate it. Fortunately my customer said his form re-appeared after syncing from another device that still had it. > * This is a perfect example of why we're moving to common core code in 2.0! And unfortunately I'm scared I'm going to be left behind until someone provides a DBAAS like Cloudant that I can redirect my customers to. -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/7d1209e8-ee24-4e9c-b040-a13415fc14cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
