Atlassian Companion not working in Edge

[TobiasR]

We have a test currently running with Confluence 6.12.

The Companion App Version 0.5.3 is working in Google Chrome and Internet Explorer but not in Microsoft Edge. Edge does not detect the installed Companion App.

This error is persistant in all domain devices (all Windows 10).

What can I do to correct this issue?

Kind regards 

Tobias

[Diego · Accepted solution]

Hello there!
The issue that you are facing might be related to the isolation technology that Windows 10 is using.
The following article states that:

- Loopback for MS Edge with Windows

MS Windows 10 uses an isolation technology ("AppContainer") that may prevent requests being sent from Edge via AppScan to your application.

e can try and enable Loopback for Microsoft Edge in Windows 10 in PowerShell. After, that we should check if the issue is still present:

CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

To run this command, we need to:

1. Shutdown Microsoft Edge
2. Run the above command in PowerShell
3.  Start Microsoft Edge again and check if the issue is resolved.

More details on loopback and troubleshooting network isolation can be found in the following Microsoft link:

-How to enable loopback and troubleshoot network isolation (Windows Runtime apps) - Windows app development

Some important points:

- this must be done by an Administrator of your environment
- this will disable the isolation implemented by Microsoft
- this may not be applicable to your environment depending on the rules/security measures enforced by the organization

Let us know if this helps you fix the issue!

[TobiasR]

Thank you, that was the solution!

[Diego]

Wonderful!

Thanks for updating us on this, Tobias. If you ever need assistance again, come share with the Community!

[Patrick Flood]

Could this be added to the documentation page for the tool?  I had separate problems with identical symptoms for Edge and Firefox and it took non-trivial googling to find this solution.

[Charles Patisaul]

Thank you @Diego, this workaround worked for me.

However, I would like to suggest that this is not a fix. It appears that the Atlassian Companion App is breaking the rules, and needs to be fixed. You're asking customers to put their computers in to debug mode in order to use your product with the built-in default browser.

From the link you provided:

Network communications using an IP loopback address cannot be used for interprocess communication (between two different apps) in a Windows Runtime app since this is restricted by network isolation.

A developer may want to use loopback for testing or debugging purposes, even though that capability will not be available for customers.

Note  Loopback is permitted only for development purposes. Usage by a Windows Runtime app installed outside of Visual Studio is not permitted.

[Deleted user]

This would break our corporate governance as well.