We appear to be missing something when it comes to a simple document read. We are using the Hotel structure presented in the documentation and one set of code works (from the documentation) and a another set of code does not (also from the docs) In referencing the documentation here Quer…

[image] visdyn: let hotelDocId = thisJsonObj["id"] as! String //crash here There is no property “id” in thisJsonObj. Unfortunately, I don’t know enough about the rest to tell you why. The Leave Feedback link on the documentation page can be used to open a ticket for the owner of the documen…

Thanks @mreiche - this code works [image] visdyn: for row in results { let docsProps = row.dictionary(at: 0)! let docid = docsProps.string(forKey: "id")! so the ‘id’ property exists on the object. Perhaps this let docsProps = row.dictionary(at: 0)! is the key but that’s not…

I don’t know why the documentation is showing you how to convert the result row to JSON and then parse the JSON to get values out of it. That’s just a very expensive no-op, compared to getting the values directly. Please don’t do that. If you’re getting a crash from an unexpected nil, then your nex…

Can you check that the document has a property name “id”? This would be an actual property, not the document id (aka document key, aka “metaId”). [image] visdyn: is the key but that’s not shown in the documentation for the second section of code. I don’t understand. It looks like it is sh…

The crashing code is parsing the query row as a dictionary and expecting it to have an “id” property. The successful code is expecting the query row to be an array whose first element is a dictionary, then gets an “id” property from the dictionary.

Thank you @mreiche and @jens We are very familiar with Swift development (knowing when to safely unwrap optionals !/?) and are trying to use the code presented in your own documentation. [image] jens: I don’t know why the documentation is showing you how to convert the result row to JSON and …

[image] visdyn: Is that documentation just wrong? Or are we missing something? Assuming you’ve copied the documentation correctly, then the documentation is wrong. When I debug things, I print out all the intermediate objects to ensure that they are what I think that they are.

[image] mreiche: When I debug things, I print out all the intermediate objects to ensure that they are what I think that they are. @mreiche Yes! We’ve gotten into that habit over the last 45 years of coding as well. :wink: But we also want to ensure we’re not ‘missing’ something or by assumi…

wasn’t sure if there was something going on under the hood with .toJSON where the crashing code should work. That’s where printing out the result would help.

[image] mreiche: That’s where printing out the resiut would help. @mreiche Perhaps I misunderstand, I thought that’s what we were doing. [print]

Documents will not read per Documentation

Mobile

visdyn October 16, 2024, 8:06pm 11

@mreiche Perhaps I misunderstand, I thought that’s what we were doing.

Topic		Replies	Views
Querying/Parsing JSON in Swift 3 query Mobile	38	4648	July 20, 2017
Question on serialization/deserialization Couchbase Lite	5	2131	February 6, 2021
Accessing CouchbaseLite document JSON Couchbase Lite mobile , dot-net	11	5210	August 10, 2020
Exception caught in map block of view - Invalid type in JSON write (_SwiftValue) Mobile mobile	4	4078	November 21, 2016
CBL Optimal Decoding & Date Decoding Inconsistencies Mobile swift	14	278	September 2, 2025

Documents will not read per Documentation

Related topics