SpatialIdRegistry Object

Global lookup of stable component and attribute IDs assigned at APK build time.

Spatial SDK components and their attributes are identified at runtime by Int IDs. Historically these came from Android resource IDs (R.id.*) populated by AAPT2 at the consuming APK's link time — which made the integers unstable across builds and consumers, breaking compiled-AAR distribution.

The new pipeline assigns deterministic IDs from 1 by post-processing the APK's component XMLs (extracted from each AAR's components directory). The result is packaged into the APK as a name → ID map asset; at process startup the bootstrap reads that asset and calls SpatialIdRegistry.install. Generated component companions then read their IDs eagerly at companion class init via SpatialIdRegistry.component and SpatialIdRegistry.attribute.

After class init the IDs are plain Int fields on the companion — accesses are single field reads, with no per-access lazy delegate, no synchronization, and no allocation.

Bootstrap order: SpatialIdsBootstrap.installIfPresent runs from VrActivity.onCreate and reads the build-time map from assets/spatial_ids.json. If the asset is present, that's the happy path: every lookup returns its build-time-assigned integer.

Transition fallback: if the asset is missing (e.g. an app that hasn't yet adopted the spatial_id_assign Buck macro / AssignSpatialIdsTask), the registry falls back to handing out IDs from a monotonic counter on first lookup and logs a one-time warning naming the missing component. The app keeps working, but IDs are unstable across runs/builds and across other apps that load components in a different order. Adopt the assigner to fix.

object SpatialIdRegistry

fun attribute(className: String, propName: String): Int

fun component(name: String): Int

fun install(componentMap: Map<String, Int>, attributeMap: Map<String, Int>)

fun reset()