Fiddler

Fiddler is a free web debugging proxy server application. You can use it to trace the communication between the Resco mobile apps and the backend server, for example, during synchronization. If you send us the communication along with the description of the problem, this can greatly speed up the troubleshooting. You just need a Windows version of Resco Mobile CRM application and Fiddler. This guide describes a simple procedure for reporting such issues with the mentioned app.

Note	Using Fiddler may decrease performance. Do not use Fiddler once you're done troubleshooting.

How can Fiddler help

• Identify server requests taking too much time
• Identify requests/responses transmitting large data
• Identify bottlenecks in the client-server communication
• Identify repeating or duplicate requests

Install and configure Fiddler

Resco Windows version

1. Download and install a Windows version of Resco Mobile CRM. You can use the store version or the desktop version.
2. Get Fiddler from the official website and install it. We recommend using the "classic" version.
3. Launch Fiddler.
4. Select Tools > Options, go to the HTTPS tab and enable Decrypt HTTPS traffic.

Windows Store only

If you are using Windows Store version of Resco Mobile CRM, perform the following additional configuration in Fiddler.

Click WinConfig on the toolbar. Click Yes in the User Account Control window. Click Yes for Loopback exemptions. In the AppContainer Loopback Exemption Utility window, find Resco Mobile CRM and enable it, then click Save Changes.

Tips for tracing

If the issue is related to any time issue, like timeout, or when it takes too long to perform the action, enable filters. Go to the Filters tab and check Use Filters.

• If you want to filter by process (recommended), check Show only traffic from and select MobileCRM:xxxx.
• Optionally, enable the option Time HeatMap. When enabled, sessions are highlighted with background color, based on how long it took for the server to respond. Fastest responses are green, average are not highlighted, slow are yellow or red.

Try to reproduce the problem. You may need to start the traffic capture manually: Select Capture Traffic from the File menu. Do so before reproducing the issue to make sure all needed data is captured. If you are successful, save the session info and send it to us for review: select Save from the File menu.

Start/Stop capturing traffic

To capture only the traffic related to our issue, start capturing traffic right before executing an action (under inspection). Stop capturing traffic right after. We have three options to start/stop capturing available:

• Click File > click Capture Traffic.
• In the Status bar, click in the left corner.
• Press F12.

Filtering sessions

Fiddler captures traffic from all processes. We can use filtering to get only those sessions we need. There are three main options to filter traffic:

• Process picker
• Status bar
• Filters tab

Process picker

Process picker is a drag-and-drop tool. Users can drag the target and drop on the process they wish to analyze traffic from.

Status bar

The Status bar offers simpler traffic filtering. You can select the process category.

Filters tab

The Filters tab offers multiple tools for how to filter traffic. The Host Filter dropdown allows you to hide, show only, and flag traffic from the specified domain.

Security

• Some companies may block Fiddler or require that it's uninstalled asap after use. The argument is that Fiddler’s root certificate can be misused by malicious apps. However, this issue is not that dramatic. The certificate is unique for the device where Fiddler is installed, hence external apps have no chance to know about it.

Fiddler and Woodford

You can use Fiddler also to trace the communication between Woodford and your backend server.

See also

• XrmToolBox - set of tools that simplify the customization, configuration, and operation of Dynamics backends