Latest Version 1.25 Not working with MCAS

[GoliathMrk1]

Hi Team

The latest version of Inspector/Reloaded is not working suspect it has a problem with MCAS(Microsoft Defender)

EDGE - error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration
CHROME - var loadTimeDataRaw = {"details":"Details","errorCode":"ERR_BLOCKED_BY_CLIENT","fontfamily":"'Segoe UI', Tahoma, sans-serif","fontfamilyMd":"'Segoe UI', Tahoma, sans-serif","fontsize":"75%","heading":{"hostName":"invalid","msg":"\u003Cspan jscontent="hostName">\u003C/span> is blocked"},"hideDetails":"Hide details","iconClass":"icon-generic","language":"en","reloadButton":{"msg":"Reload","reloadUrl":"chrome-extension://invalid/"},"suggestionsDetails":[],"suggestionsSummaryList":[],"summary":{"failedUrl":"chrome-extension://invalid/","hostName":"invalid","msg":"This page has been blocked by Chrome"},"textdirection":"ltr","title":"chrome-extension://invalid/"};

Utilizing Inspector Reloaded 1.25 on Edge/Chrome and api version 60 and 62 tried on windows 11

[tprouvot]

@GoliathMrk1 seems that you are using a connected app aren't you?

[GoliathMrk1]

Hi Tprouvot,

Yes we do use connected apps, just not sure how that relates? could you explain or point me in the right direction?

Thanks for the quick response!

[tprouvot]

Have you created a custom connected app or using the default one coming with Reloaded ?
Have you followed the steps mentionned in the documentation ?

[GoliathMrk1]

We didn't create a custom connected app, and I see the default inspector reloaded connected app is not installed.

will follow the documentation and revert

[tprouvot]

Let me know if the how to allowed you to solve the issue

[GoliathMrk1]

Hi tprouvot

after installing the inspector reloaded connected app we are still seeing the same issue.

[tprouvot]

Could you paster the anonymized url when you are redirected to data-export page ?
It seems that there is a mismatch between the current url and the expected on in the callback url of the connected app