Gather Logs: Background Console and Network logs and Client Console logs – Zendesk for Arrow Electronics

When facing more complex issues, we might ask for logs. These logs give us valuable data and insights, helping us better understand and resolve the issues you might be encountering.

This article contains a full set of guidelines and visual aids to gather more info using Arrow debugging tools and extension Background Console and Network Logs and Client Console Logs.

Web Solutions

The first section refers to diagnostics logging, a tool that helps developers understand how the Arrow Smart Extension functions behind the scenes. This tool is invaluable for debugging customer issues. Diagnostics logging offers a more secure and efficient way to gather data about issues you're having and is the preferred method for information collection.

The second section provides instructions for collecting Background Console and Network Logs and Client Console Logs. These methods have more steps and should only be used when specifically instructed, as the diagnostic logging tool is the preferred option.

Diagnostic logging tool

You need extension version 6.2449 or later to use this tool. Once enabled (following the steps below), the tool will remain active for seven days before automatically disabling.

Steps to enable diagnostic logging:

Ensure your Arrow Smart Extension is running at least version 6.2449.
Right-click the Arrow D icon in your browser toolbar.
- Chrome: Select Options in the drop-down menu.
- Firefox: Select Manage Extensions, select the 3-dot icon, and then select Preferences.
- Edge: Select Extension Options in the drop-down menu.
- Safari: Select Manage Extensions and then select Settings.
Click three times on the Troubleshooting header.
A toggle appears. Enable diagnostic logging for the next seven days.
Please share the Diagnostic ID that appears in the extension information section by email so that we can provide the Engineering team with details to assist with the investigation.

Important:

Keep the extension running for at least 15 minutes after experiencing the problem
Let us know the exact time you encountered the issue

Background Console and Network Logs and Client Console Logs

Difference between types of logs

Background Console and Network Logs: Gathered for issues with the extension loaded, for example, unable to log in, failed login, or error on the login and display on the extension itself.

Client Console Logs: This one collects the logs from the web app, for example, when you're unable to complete the login or see an error message when doing a login on the web app or web view.

If you take a few moments to watch the videos available for each one, you'll notice the difference in how they're gathered.

Warning! Collecting these logs may require a logout in some cases.

In such cases, before logging out, make sure you're logged in on at least one other device or have access to an account recovery key. Otherwise, you might lose access to the account.

Background Console and Network Logs

This section provides the specific steps to gather Background Console and Network Logs with short recordings for the supported browsers.

From Chrome or Chromium browsers

Be sure that you aren't logged in on the extension. The Arrow D should be red.
Right-click the Arrow extension and select Manage Extension.
Turn on Developer mode. The location will depend on the browser.
From there, select service worker under Inspect views. If in Edge, you'll see Background page instead.
DevTools opens in a new window.
In the top menu bar, be sure to have Network selected.
Go back to the browser window and attempt to log in to Arrow.
Go back to the DevTools window.
In the top menu bar, select the Export HAR icon, shown as a down arrow in a square.
Select a location where you can save it and retrieve it later.
Still in the DevTools window, in the menu bar, go to Console.
Right-click after the last entry on the log and select save as.
Select a location where you can save it and retrieve it later.
You can now close the DevTools window and turn off Developer mode on the extension.

From Firefox

Be sure that you aren't logged in on the extension. The Arrow D should be red.
Right-click over the Arrow extension and select Manage Extension.
On the top, select the gear icon to open the extension settings.
In the list, select Debug Add-ons.
In the new tab, Debugging, look for Arrow under Extensions and select Inspect to the right.
A Developer Tools window opens that shows the Console and Network logs, among others.
Select the Arrow extension that should still be red and attempt to log in.
Go back to the Developer Tools window.
In the logs menu, select Console, and you'll see a list. Right-click anywhere on that list and select Save all Messages to File.
Select a location where you can save it and retrieve it later.
In the logs menu, select Network. You'll see another list. Right-click anywhere on that list and select Save All As HAR.
Select a location where you can save it and retrieve it later.
You can now close the Debugging tab and the Developer Tools window.

From Safari

Open Safari's preferences (Safari menu in the top browser bar and then select Settings) and select the Advanced tab.
In the Advanced tab, select the box on the bottom: Show features for web developers.
After the Develop menu is enabled, you'll open it from the Web Extension Background Content > Arrow.
Web Inspector - Arrow opens in a new window, automatically on the Console tab.
Change to the Network tab and select refresh, shown as a circle with an arrow tip, in the top left icons. Wait for about 5 seconds.
Go back to the extension and reproduce the issue you're experiencing.
Go back to Web Inspector - Arrow, and you should still be on the Network tab.
Select the Export option in the top right of this window.
Select a location where you can save it and retrieve it later.
Still in Web Inspector - Arrow, go to Console.
Select any entry in these logs and then press Command + A, or go to Edit > Select All to select everything.
Then right-click anywhere on the selected logs and select Save selected to save all the logs in a TXT file that you can send.
You can now close the Web Inspector - Arrow window and disable Show features for web developers in Safari's settings that you enabled at the beginning.

Client Console Logs

This section provides the specific steps to gather Client Console Logs with short recordings for the supported browsers.

From Chrome or Chromium browsers

Be sure that you aren't logged in on the extension. The Arrow D should be red.
In the address bar, enter "app.dashlane.com"
If necessary, enter your Arrow ID email address.
Right-click in the Master Password field and select Inspect at the bottom of the list.
A new section opens, usually to the right. Select Console in the logs menu.
Go back to the Master Password field and attempt to log in.
You'll get an error, or you'll be able to log in.
Go to the section on the right that shows the logs. Right-click over one of the entries in the list of messages and select Save as.
Select a location where you can save it and retrieve it later.
You can now close the logs section with the X in the top right or close Chrome.

From Firefox

Be sure that you aren't logged in on the extension. The Arrow D should be red.
In the address bar, enter "app.dashlane.com"
Right-click in the Master Password field and select Inspect at the bottom of the list.
A new section opens at the bottom. Select Console in the logs menu.
Go back to the Master Password field and attempt to log in.
You'll get an error, or you'll be able to log in.
Go to the section below. Right-click on one of the entries on the list of messages and select Save all Messages to File.
Select a location where you can save it and retrieve it later.
You can now close the section below with the X in the top right or close Firefox.

From Safari

Open Safari's preferences (Safari menu in the top browser bar > Settings) and select the Advanced tab.
In the Advanced tab, select the box on the bottom: Show features for web developers.
In the address bar, enter "app.dashlane.com"
Right-click in the Master Password field and select Inspect at the bottom of the list.
A new section opens at the bottom. Select Console in the logs menu.
Go back to the login page and reproduce the issue you're experiencing.
Go to the section below that should still be in Console.
Select any entry in these logs and then press Command + A, or go to Edit > Select All to select everything.
Then right-click anywhere on the selected logs and select Save selected to save all the logs in a TXT file that you can send.
You can now close the Web Inspector - Arrow window and disable Show features for web developers in Safari's settings that you enabled at the beginning.

Android Solution

Android debugging tool

This section provides the specific steps to gather diagnostic files from the Android app in a streamlined, secure way.

Note: The server will keep the log files for 14 days, and then the files are deleted.

Launch the Arrow Android app on your phone.
Select Use another account and, instead of the login email address, enter “diagnostic”.
Select Continue and then OK to confirm.
After the Upload successful message appears, select Copy for the Debug ID.
Please share the Debug ID by email so that we can provide the Engineering team with details to assist with the investigation.

iOS Solution

iOS debugging tool

This section outlines the steps to enable Diagnostic Mode for Arrow in the iOS device system settings. Activating this mode allows access to crash reports that are stored on the device, which can then be shared with the Apple team upon their request.

Note: Enabling Diagnostic Mode for Arrow in the system settings adds a “Debug Information” button to each vault item. The button opens a sheet with options to copy all debug info or take a screenshot, which can be easier for some people. Additionally, individual fields can be copied using the menu.

Open the Settings app on your device.
Scroll down and select Privacy & Security.
On the Privacy & Security screen, scroll down and select Analytics & Improvements and then Analytics Data.
From the list, open the most recent crash related to Arrow. The crash reports are sorted by app and date, and the most recent report is at the end of the list.
Select the Share icon, shown as a square with an up arrow, in the upper-right corner of the screen.
Please share the file by email so that we can provide the Engineering team with details to assist with the investigation.