What are logs?
Logs are text files stored on your device that include information about Waze app usage. Logs help us fix problems by giving us more information about what happened.
Note: Logs are limited in size and are cyclically overwritten – so if you want to include logs in a bug report, make sure to submit the report and logs as soon as possible after you experience a problem.
What information do logs include?
-
The flow of actions that a user performed
For example: What buttons were tapped and when, and what was shown on screen -
Information about, and content from, the communications that took place between the app and Waze’s servers
For example: A detailed GPS location for your previous route, such as a route that was requested from point A to B and what route was offered in response -
Information related to the user's device and locale
For example: Device type, operating system version, location, language, application crash information, etc -
A user’s profile, preferences saved in Waze settings, and other user info
For example: Preferred display settings, preferred Gas station, etc.
Passwords and sensitive payment-related information are not stored nor included in logs.
When investigating a bug, we want to understand how and why it happened. Log files contain all the information debug mode collects. They are only created when your device has Debug mode enabled.
How are logs used?
When you choose to submit logs, our test engineers review them to better understand what sequence of actions led to the bug or problem that you experienced.
Then, once and if our engineers define which component of the service caused the bug, they can open a request to fix it. As soon as a bug fix is made and released, it is available to all Waze users.
Debug mode
In the past, Waze beta testers were asked to enable Debug mode on their phones, so they could share their log files when needed. Starting October 2020, All versions of Waze (Beta, RC, Store release) have Debug mode enabled, for Wazers flagged as Beta community members. There's no need to manually enable Debug mode.
Debug mode ensures that if you encounter a bug, you'll be able to provide log files.
Enable / Disable debug mode
Update October 2020: All versions of Waze (Beta, RC, Store release) have Debug mode enabled, for Wazers flagged as Beta community members. There's no need to manually enable Debug mode.
- In the Waze app Search bar
, search for 2##2
- Close Waze. Make sure it's not just minimized but actually closed
- Next time you open Waze, the debug status will change
Submit Waze Log Files
Was debug mode enabled when you encountered the bug? Great! Here's how you submit logs:
- Tap Reports > Bee icon
- Enable debug mode
- Close the app
- Reopen the app
- Reproduce the bug
- Send log files following the steps mentioned above.
Unable to submit debug logs?
- Android - Logcat - available in the PlayStore
- iOS - Diagnostic logs - Internal iOS tool
Device logs
For certain issues, we will ask for your device logs which are different than Waze logs. Here's how you can get those:
Submitting iOS device logs
- Open your phone's Settings and tap Privacy > Diagnostics & Usage > Diagnostics & Usage Data.
- Scroll through and check if any of the entries have Waze in the title. If any of the titles include the word Waze, please tap on the entry and select all of the text and paste it into an email to send to yourself, then include the text in your bug report.
Submitting Android Device logs
- Open your phone Settings and tap About phone.
- Tap Build number 7 times until you receive a popup asking if you’d like to be developer, click Ok to approve the message. If this doesn't work for you, please look up "Enabling developer mode + your device model".
- Go back to phone Settings and tap Developer options.
- Enable USB debugging and tap Ok.
- Go back to your home screen and open Waze.
- Open phone Settings again and tap Take bug report.
- Wait for logs to download, this could take a few minutes. Once the logs have downloaded (you should receive a notification), tap the notification and send it to yourself to attach to your bug report in Centercode.