We are actually using Xamarin with CBL iOS, since we have started with TouchDB even before CBL.NET was around.
On Tuesday, September 12, 2017 at 3:22:22 PM UTC-7, dyowee wrote: > > I understand sir. Thank you for your input. Will try your suggestions. > > On Tuesday, September 12, 2017 at 3:06:58 PM UTC-7, Jens Alfke wrote: >> >> >> >> On Sep 12, 2017, at 2:03 PM, dyowee <[email protected]> wrote: >> >> I understand sir. What about the size/length of the json string? Would >> that cause an issue/crash? >> >> >> No. The method is not supposed to crash, period. (Unless it's given a bad >> pointer, or the heap has been corrupted or something, of course.) >> >> There are three possibilities: >> >> 1. CBL is passing a bad pointer or a dealloced object or something >> like that. >> 2. There's a bug in Apple's NSJSONSerialization implementation. >> 3. Some code in your app has corrupted the heap. >> >> >> 1 seems unlikely because you're the only one to have reported this bug, >> so apparently it doesn't happen in other people's apps. Also, a bug like >> this tends to crash immediately in the Obj-C runtime the first time the bad >> object is called. >> 2 also seems unlikely given how many developers Apple has, and that the >> NSJSONSerialization code has been around for about six years. >> As for 3, have you used the Xcode Address Sanitizer and Static Analyzer >> to look for potential memory bugs? >> >> —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/dae419c5-153f-4fd9-831b-0b03d76b626a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
