Fiddler: Difference between revisions
No edit summary |
|||
| Line 7: | Line 7: | ||
# [[Resco_Mobile_CRM#Download|Download]] and install a Windows version of [[Resco Mobile CRM]]. You can use the store version or the desktop version. | # [[Resco_Mobile_CRM#Download|Download]] and install a Windows version of [[Resco Mobile CRM]]. You can use the store version or the desktop version. | ||
# Get Fiddler from [https://www.telerik.com/fiddler the official website] and install it. | # Get Fiddler from [https://www.telerik.com/fiddler the official website] and install it. | ||
# Launch Fiddler. | |||
# Select '''Tools > Options''', go to the '''HTTPS''' tab and enable '''Decrypt HTTPS traffic'''. | # Select '''Tools > Options''', go to the '''HTTPS''' tab and enable '''Decrypt HTTPS traffic'''. | ||
Revision as of 09:45, 26 July 2019
Fiddler is a free web debugging proxy server application. You can use it to trace the communication between the mobile CRM app and the CRM server. 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. |
Install and configure Fiddler
- Download and install a Windows version of Resco Mobile CRM. You can use the store version or the desktop version.
- Get Fiddler from the official website and install it.
- Launch Fiddler.
- 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. |
|
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, check Use Filters and then enable the option Time HeatMap.
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.