Hi Colin Harper,

Is it possible to use Fiddler to capture the call for which the status code is (404)? Somehow the plugin is trying to make a call to a specific URL, it will be good to see which URL is not working. 

Do you have a logging mechanism in the plugin? This will help us to troubleshoot the problem.

Kind regards,

Andrea Ghisa

Hi Andrea,

I just installed a logging mechanism (NLog) in the plugin yesterday.

What do you recommend we log before we deploy it?

Perhaps each URL requested? Although the logs might bloat up quickly if that level is recorded.

Would just the error message from the error response and the URL requested be sufficient?

Regards,

Colin

Hi Colin,

If you are using HttpClient you can use EnsureSuccessStatusCode() method. This will throw an error if the call is unsuccessful, log from that exception anything which is useful for troubleshooting: status code, response message, request Uri and so on.

I would recommend using this approach on every service call you have in the application. 

Documentation:

• https://docs.microsoft.com/en-us/uwp/api/windows.web.http.httpresponsemessage.ensuresuccessstatuscode?view=winrt-19041
• stackoverflow.com/.../usage-of-ensuresuccessstatuscode-and-handling-of-httprequestexception-it-throws

Adding these logging details to the client's account gave us the info we needed to resolve the issue.

The configuration form was attempting to use a value from the plugin options settings that had not been set yet. The reason it worked on all our installations was that we had previously installed older versions of the plugin which had set the plugin options which meant there was a value stored there.

When the other user tried to use the plugin for the first time there were no previously-stored plugin options so the plugin produced the above error.

Thanks again for your help Andrea

Adding these logging details to the client's account gave us the info we needed to resolve the issue.

The configuration form was attempting to use a value from the plugin options settings that had not been set yet. The reason it worked on all our installations was that we had previously installed older versions of the plugin which had set the plugin options which meant there was a value stored there.

When the other user tried to use the plugin for the first time there were no previously-stored plugin options so the plugin produced the above error.

Thanks again for your help Andrea

Hi Colin Harper,

I'm glad you found the problem and now is working on user machine.

Have a nice day,

Andrea Ghisa