Debug View in MazeMap App
Somewhat outdated or overlapping with new documentation page:
https://mazemap.atlassian.net/wiki/x/NQAJmw
Native app debugging is available only to the administrators of the MazeMap app in their respective campuses because you need a special key/link from MazeMap.
Web app debugging is technically visible/accessible for end-users without a special key, but currently only for campuses/configs where it is enabled. (Needs enabling from Engineers)
New webapp debugging view is documented here: https://mazemap.atlassian.net/wiki/x/NQAJmw
A. Make sure that the GPS is activated on your device. (You will be prompted about this in both IOS and Android devices)
B. Make sure your device uses the right network (with positioning service).
C. Make sure you have the latest, most stable version of the MazeMap app (version 5.2.23)
D. Open the MazeMap app using the following link. mazemap://use.mazemap.com/?enable_native_debug=DgYFBwsAAAwCBQgABAoCCw
This older version of the debug link above still works https://use.mazemap.com/?v=1&campusid=47&enable_native_debug=DgYFBwsAAAwCBQgABAoCCw in case, tester knows the exact campus id of their organization.
This link will give you access to some debug information that is valuable to us. By default, CMX has priority over IndoorAtlas. The app will then try to use LIPI first and then IndoorAtlas. Please follow the following steps:
- Click on the link: https://use.mazemap.com/?enable_native_debug=DgYFBwsAAAwCBQgABAoCCw or https://use.mazemap.com/?v=1&campusid=47&enable_native_debug=DgYFBwsAAAwCBQgABAoCCw
If it does not open the MazeMap app automatically, you should get the opportunity to choose which app to open the link: - Choose the MazeMap app.
- On the top of the app you will get a button to a debug view. Click on this to expand it
4. You will now get some debug information in the top part of your screen. You can see the current location you have, the z-level and the accuracy of the position.
NB: Accuracy rate shows how close the device’s calculated position is from the truth expressed in radius. So the lower the number, the higher the accuracy
Location update count should be rising
GPS fallback location update count should be as close to 0 as possible (the "?" usually appears when GPS Fallback count or accuracy index rise)
If you scroll down that upper section you will see the available positioning methods (with their priorities) in your campus. As you can see from the screenshots below, LIPI that has the highest priority.
(NB: The higher the number, the higher the priority)
This Debug View will make it possible to compare the results from the two solutions and give you the right information to choose which to prioritize.
You can also see enabling buttons: LIPI, INDOOR_ATLAS, CMXHYBRID, CLOUDPOS, GPS, AUTO.
IndoorAtlas-specific information
In case the customer is specifically debugging the IndoorAtlas performance, the TraceID of the testing session is now visible on the view (see upper portion of the screenshot below) . It lists the latitude, longitude, accuracy, Z level, timestamp and Trace ID, which they could then copy by pressing the blue button "Copy TraceID" and then send to IndoorAtlas for support.
Cloud Positioning (DNA Spaces)
1. Download the MazeMap app on your phone
3. Select 'Expand debug view' in the app.
4. Choose 'Cloud Positioning' as the positioning provider.
5. Collapse debug view
5. In case you prefer one method over the other, you can send a service request ticket to support@mazemap.com with the instruction to give higher priority to one and we will do it as soon as possible.