deliverableTo

fun Map<String, JsonElement>.deliverableTo(receiver: Any): Map<String, JsonElement>

These properties as receiver can take them: unchanged for a receiver written in Kotlin, and with every nested object or array value replaced by its JSON text for one written in Swift or Objective-C (#299).

A Swift Tracker or Transport cannot receive a nested value at all. Kotlin/Native hands a JsonObject value across as an NSDictionary and a JsonArray value as an NSArray, not as the JsonElement the signature promises, and Swift converts the whole [String: JsonElement] dictionary as the call enters it, so the process traps before the conformer's body runs — whether it reads the value or not. A JSON string is what __autograph (#298) and the Segment bridge already send for the same reason, and a Swift conformer can decode it with JSONSerialization. Primitive values, null included, cross intact and are left alone. The replacement loses the type: a Swift receiver cannot tell an encoded object from a string value that happens to hold the same JSON text, so it should decode a value only where it knows that key carries a nested value.

Every call Autograph's own modules make on a Tracker, Transport or EventValidator passes its properties through this, so a Kotlin receiver keeps getting real objects and arrays, and LocalTracker is covered through callableFromKotlin. A call that does not go through Autograph — Kotlin code that holds a Swift tracker and calls it directly, or a Kotlin wrapper forwarding to a Swift transport — is not covered and still traps.

@AutographInternalApi: public only so autograph-compose, autograph-context and autograph-uikit can apply it at their own call sites.