SDK error codes - OneS1ght

Error code summary

Code family	Area
`1xxx`	SDK initialization and authentication
`2xxx`	Mobile device
`3xxx`	Spatial data
`4xxx`	Positioning
`5xxx`	Communication with OneS1ght servers
`Ixxxx`	SDK activity notices

1000s — SDK initialization and authentication

Code	Meaning
`E1001`	SDK initialization failed.
`E1002`	Invalid SDK API key.
`E1003`	Positioning data has not been configured in the console.
`E1004`	No profile has been registered for the mobile user.

2000s — Mobile device

Code	Meaning
`E2001`	Unsupported iOS version.
`E2002`	The device does not support Nearby Interaction.
`E2003`	Nearby Interaction permission has not been granted.

3000s — Spatial data

Code	Meaning
`E3001`	No floor has been selected for collecting positioning data.
`E3002`	The selected floor has no locators.
`E3003`	No session data was found for the selected floor.
`E3004`	The selected floor has no zones.

4000s — Positioning

Code	Meaning
`E4001`	No session was found for the selected floor.
`E4002`	The registered coordinates do not match the actual layout of the space.
`E4003`	Some locator signals could not be found.

5000s — Communication with OneS1ght servers

Code	Meaning
`E5001`	Cannot reach the network.
`E5002`	An internal server error occurred on the OneS1ght side.
`E5003`	Please update the SDK to the latest version.
`E5004`	API key authentication failed.
`E5005`	No response was received from the server.
`E5006`	Coordinate data could not be sent.

SDK activity notices

Activity notices are not errors — they are informational logs about what the SDK is doing internally.

Code	Meaning	Example
`I1001`	Initialization complete	`tenant=…`
`I1002`	Profile connected	—
`I3001`	Floor selected	`building=… floor=… locators=N zones=M`
`I4001`	Positioning started	`visitor=v-20260820-001`
`I4002`	Positioning stopped	`visitor=… points=N`
`I5001`	Upload rate applied	`rate=20` (only when it differs from the default of 4)

To debug communication with the UWB locators, see the guide below.
Guide — How to collect logs