Theo Kallioras

@pavelnikolov Sorry for the delayed reply. Here is a type with a field (**multipolygon**) that produces the issue ``` type GeoJSON { type: String! boundingbox: [Float!] point: [Float!] multipoint: [[Float!]!]...

@dmitshur is there any chance that the solution by @adamgoose be added in the package?

I would also be interested in seeing this implemented.

@pavel-ship-it Thanks for responding. I will share a detailed stack, a screenshot of the memory consumption (which as you can see doesn't increase) and a screenshot of the memory references...

@pavel-ship-it Is there a possibility that there is something else except memory? If you take a look at the screenshot I attach, the memory is not increasing, neither is it...

@pavel-ship-it @tgoyne @ericjordanmossman We managed to limit the issue a lot. It was unrelated to `writeAsync` (@ericjordanmossman you mentioned our issue in #7817, but it wasn't the `writeAsync` after all)....

@tgoyne @pavel-ship-it I just saw that the [12.4.0 version of realm core](https://github.com/realm/realm-core/releases/tag/v12.4.0) contains a possible fix for this case. Do you know if it be included in the next release...

We have encountered the exact same problem. Whenever we try to eager load sibling relationships using `.with` and then `.all` it always triggers the `Cannot access field before it is...

@karola-gr sorry for the delayed reply. Unfortunately no. I cannot eager load any sibling relationship. It doesn't fail sporadically, it fails consistently, and I can't find a workaround.

I have the exact same issue with Azure, and I haven't added any SwiftLint products in the target. It's only added as a plugin during build phase, but still, I...