The session summary returned by the Data API contains a list of possible issues, useful for troubleshooting positioning performance. While the API only returns concise issue identifiers, in this article we describe the issues in more detail and give suggested troubleshooting actions. The issues are also visible in the Session Viewer.


The detailed structure of the session summary can be viewed in the Data API documentation.


Note that the session summary and thus also the troubleshooting items are not available if the used API key has temporary data storage. To review your data storage options, see here.


Old SDK version (oldSdkVersion)


To enable best possible positioning experience, it is recommended to always use the latest IndoorAtlas SDK to take advantage of the latest added features and performance improvements. This issue is raised if a newer major or minor version of the SDK has been released.


For information on the latest IndoorAtlas SDK, refer to our developer docs site.


Missing required sensors (missingRequiredSensors)


To enable the full IndoorAtlas experience, it is required that the devices used in positioning have the inertial sensors (accelerometer and non-virtual gyroscope), and a magnetometer. This issues is raised if any of these are missing. Devices lacking the required sensors can still be used in radio-only positioning.


Missing position outputs (missingPositionOutputs)


This issue is raised if the IndoorAtlas SDK was not able to determine your position. Possible reasons for this:

  • You are far away from a fingerprinted indoor location.
  • You are using incorrect IndoorAtlas credentials. Verify that the used API key is on an account which has fingerprinted IndoorAtlas locations.
  • There is some issue with radio scanning or getting platform location in the used device. Either a radio scan or platform location is required for the SDK to get a rough idea of the user's position and to initialize positioning.
  • There is some issue with the fingerprinting. For example, if there were no radio observations during fingerprinting, radio scans cannot be used to initialize positioning. Check the mapping analytics in the IndoorAtlas web tool and see here for more information on the analytics.


Missing floor plan context (missingFloorPlanContexts)


This issue is raised if no floor plans were recognized during the session. This can be caused by similar reasons as missingPositionOutputs.


If your use case does not require indoor-outdoor transitions, you can consider setting indoor lock on to force the position esimate indoors, or locking the floor to the desired value. Check the SDK documentation for more details.


Missing venue (location) context (missingVenueContexts)


This issue is raised if no venue (location) context was recognized. Possible causes are similar as in the above two issues.


Missing Wifi inputs (missingWifiInputs)


This issue is raised if no Wifi observations were heard during the session. Note that iOS devices do not allow Wifi signals to be listened to, so this issue can be ignored on iOS. To troubleshoot this issue on Android, check that Wifi scanning is enabled on your device, and that precise location permission is given to the application running IndoorAtlas.


Missing BLE beacon inputs (missingBeaconInputs)


This issue is raised if no BLE beacon observations were heard during the session. To troubleshoot it, check that Bluetooth scanning is enabled in your device, that your app has permission to scan Bluetooth, and that there are BLE beacons (transmitting iBeacon or Eddystone protocol) in the environment.


If you manage the beacon installation in your location, check that the beacon are physically there and still transmitting.


Missing platform location inputs (missingPlatformLocationInputs)


This issue is raised if no platform location inputs were observed during the session. This includes satellite navigation systems such as GPS, or a network location which may use cell tower signals or other radio sources, depending on the platform. Please check that location services are enabled and that the app has permission to read the platform location.


Note that platform location is usually inaccurate indoors, and at least satellite based navigation may be completely unavailable deep inside large buildings, for example in parking garages.


Location services not available (missingLocationPermission)


IndoorAtlas positioning requires user permission to use the platform location services. Make sure your app requests the appropriate permissions. On Android devices you need the precise location permission.


Bluetooth scanning not available (missingBluetoothPermission)


To enable the use of BLE beacons in positioning, Bluetooth scanning must be enabled on the device and the app needs user permission to use that data.


Wifi scanning not available (missingWifiPermission)


To use the Wifi environment in positioning, Wifi scanning must be enabled on the device and the app needs user permission to use the data.