You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I can not open and edit my Excel document using the Confluence Atlassian app. It was working up to the beginning of this week. I'm not sure if it was a Chrome update or an Atlassian update but I keep getting a prompt to reinstall the app. I have uninstalled, rebooted and then reinstalled and still get the same issue
Thanks for raising this issue. The most likely cause of Companion not working since upgrade to 2.0.0 and above is the fact that Companion 2.0.0 drops support for a legacy way of communicating with Confluence (via Websockets). Confluence 7.3.0 and below require Companion to use Websockets to communicate with the Confluence UI.
The recommended solution is to upgrade Confluence to any currently supported version.
Alternatively, another solution may be to downgrade Companion to 1.6.1 which is the last version to support Websocket communication. However, since we do not test Companion against versions of Confluence that have reached their end of life, there is the potential for other issues with this approach.
We strongly recommend always using a supported version of Confluence with the latest version of Companion to get access to the latest security and bug fixes.
Senior Engineering Manager, Confluence DC
Here is a download link https://update-nucleus.atlassian.com/Atlassian-Companion/291cb34fe2296e5fb82b83a04704c9b4/_index/1.6.1/win32/ia32/Atlassian%20Companion-1.6.1.msi . You should use MSI installer as it won’t do auto upgrade.
I was able to get this deployed to our end users and haven't had any issues since installing this.
Seeing the same issue on our end which seems to have started after a chrome update. Any recommendations?