When it happens again (and I'm sure it will) I'll capture the request info from Charles Proxy. I had to delete the attachment to continue on with my work and the problem vanished for now when I replaced the attachment.
But it does keep coming back. On Monday, August 22, 2016 at 12:35:34 PM UTC-6, Jens Alfke wrote: > > > On Aug 22, 2016, at 10:26 AM, Brendan Duddridge <[email protected] > <javascript:>> wrote: > > Actually in the full error message that I posted, the error did say > "missing_stub": > > > Oh, sorry. In that case it refers directly to the “stub”:true property > that appears in the attachment metadata to indicate that the body of the > attachment is deliberately not being sent. (The alternatives are to send > the data inline by adding a “data” property, or by adding a “follows”:true > property to indicate that the data is in a separate MIME part.) > > Is there a way you can capture the entire request that produced the error, > by using HTTPScoop or Charles Proxy or something? > > —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/3ce90a80-670b-45de-a19f-874f2b60305c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
