Hm, attachments. Good point. Internally, the way that method gets used is that the attachment bodies are downloaded into the attachment store first, and then when the revision is added (with the _attachments property intact) they’re already there so the insert succeeds. But there’s no public API for shoving attachments directly into the store (nor should there be.)
As a workaround for right now, you can preprocess the attachment metadata to put the data inline: - remove the “follows” or “stub” properties - base64-encode the attachment body - add a “data” property whose value is the base64 string Then call putExistingRevision… I should come up with a better way to do this, though, before we release this API. I filed #1195<https://github.com/couchbase/couchbase-lite-ios/issues/1195>. —Jens -- 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/2A0BC30E-E84A-4260-B959-BCE7391D8473%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
