Skip to content
Select language:English

Throubleshooting

Updated 3 min read

This page provides a guide on handling errors related to the MDK. If you don’t find a solution, you can request support from the GiPStech Team by following the instructions at the end of this page.

The MdkException class contains three main categories of exceptions:

  • Core: representing exceptions generated within the Core library.
  • Sensor: representing exceptions arising from anomalies or errors in sensor data.
  • Network: representing errors encountered during the connection to the GiPStech Server.

Exceptions can either be thrown directly when calling any API function or be delivered via LocationListener.onException events if they occur during localization.

Core exceptions should not occur under normal circumstances. They may be caused by a corrupted file or an incorrect configuration of the GiPStech location engine. If you suspect the issue is due to a misconfiguration, please contact GiPStech support.

Sensor exceptions may occur if a sensor is temporarily disabled by the user (for example, if Bluetooth or location services are turned off, or the corresponding permission has not been granted). In rare cases, exceptions may result from a malfunctioning physical sensor, which could indicate that the device is damaged. In some situations, the issue can be resolved simply by rebooting the device.

The name of the sensor is indicated in MdkException.Sensor.sensorName property.

Network exceptions include a subtype called BadResponse. Subclasses of this type indicate that the server successfully processed the request but returned an unsuccessful response.

The accuracy of location estimates depends on various factors, as GiPStech technology integrates multiple signal sources. If you experience poor accuracy, consider the following:

  • Georeferencing: Ensure that floors have been correctly georeferenced via the GiPStech mapping portal and that all relevant data (including beacons, walls, etc.) have been properly entered.
  • Bluetooth Beacons: If using Bluetooth beacons, verify that they have not been moved and that their batteries are not depleted. You can check this using the GiPStech Mapper app.
  • Geomagnetic Positioning: If using geomagnetic localization, confirm that the magnetometer calibration has been performed correctly. If the “fast” calibration is insufficient, try a “full” calibration, aiming for at least 80% completion - make sure to stay away from ferromagnetic materials during this process.
  • Visual Positioning: Ensure there is adequate lighting, the camera is unobstructed, and it is facing forward.
  • Radio Signals: Verify that there are no sources of interference affecting the signals.
  • Inertial Navigation: If using the inertial engine, ensure that the movement is pedestrian and that the phone is held in hand, positioned in front of the user.

The GiPStech MDK is not thread-safe, as ensuring thread safety comes with a performance cost that is unnecessary for most typical usage scenarios of this API.

Therefore, it is mandatory to avoid invoking any functions of this API in parallel.

That said, the MDK does implement some internal synchronization mechanisms. For example:

However, certain operations are mutually exclusive and must not be executed simultaneously (e.g. running two localization processes or initiating a calibration while a localization is ongoing). These constraints are only enforced at the start of each operation, based on the system’s current state.

As a result, starting such operations concurrently in different threads can lead to undefined or unexpected behavior.

If you need GiPStech technical support, you can submit a ticket through our Help Desk (opens in a new tab).

If you have encountered a bug in the MDK, please include the following details in your report:

  • Device name and manufacturer
  • Operating system version
  • GiPStech MDK version
  • Name and version of the IDE/Compiler used to build the app
  • A brief description of the steps to reproduce the issue
  • A sample application that replicates the bug

The last point is mandatory. The sample application must include the complete project files along with the source code, which should be as minimal as possible. Ideally, it should contain only the necessary calls to the GiPStech MDK, avoiding third-party libraries whenever possible.