Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57445

Disable update check for Companion App MSI

XMLWordPrintable

    • 4
    • 4
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The Page Administering the Atlassian Companion App states that by using the MSI, the app won't automatically get the updates.

      If you deploy using the Microsoft Installer, the Companion app won’t automatically get the latest updates, including security and bug fixes, so some maintenance is required.

      While this is true, the logs are flooded with update checks on every few minutes

      {"namespace":"adc:auto-updater","date":"2018-10-29T09:46:05.590Z","message":["update error",{"message":"Can not find Squirrel","stack":"Error: Can not find Squirrel\n at AutoUpdater.emitError (C:
Program Files (x86)
Atlassian Companion\\resources\\electron.asar\\browser\\api\\auto-updater\\auto-updater-win.js:70:24)\n at AutoUpdater.checkForUpdates (C:
Program Files (x86)
Atlassian Companion\\resources\\electron.asar\\browser\\api\\auto-updater\\auto-updater-win.js:41:19)\n at Timeout.setTimeout [as _onTimeout] (C:
Program Files (x86)
Atlassian Companion\\resources\\app.asar\\src\\browser\\autoUpdater.ts:38:67)\n at ontimeout (timers.js:475:11)\n at tryOnTimeout (timers.js:310:5)\n at Timer.listOnTimeout (timers.js:270:5)"}]},
{"namespace":"adc:auto-updater","date":"2018-10-29T09:51:05.604Z","message":["update error",{"message":"Can not find Squirrel","stack":"Error: Can not find Squirrel\n at AutoUpdater.emitError (C:
Program Files (x86)
Atlassian Companion\\resources\\electron.asar\\browser\\api\\auto-updater\\auto-updater-win.js:70:24)\n at AutoUpdater.checkForUpdates (C:
Program Files (x86)
Atlassian Companion\\resources\\electron.asar\\browser\\api\\auto-updater\\auto-updater-win.js:41:19)\n at Timeout.setTimeout [as _onTimeout] (C:
Program Files (x86)
Atlassian Companion\\resources\\app.asar\\src\\browser\\autoUpdater.ts:38:67)\n at ontimeout (timers.js:475:11)\n at tryOnTimeout (timers.js:310:5)\n at Timer.listOnTimeout (timers.js:270:5)"}]}

      Please remove the update check for the MSI version of the App.

            [CONFSERVER-57445] Disable update check for Companion App MSI

            Alex K added a comment -

            alexander.greig-more

            As of Companion 0.6.0, there will be a companionConfig.json file in the Atlassian Companion/resources directory. 

            Could you please verify the contents of this file?

             

            For the MSI install, this file should contain the following:

            {"builtWith": "wix"}

            For the EXE install, the file should contain:

            {"builtWith": "squirrel"}

             

            If the config file exists and matches that of what it should be for the MSI install, you will see the following log message:

            "message":["Application was installed via MSI, not watching for updates"]  

            Alex K added a comment - alexander.greig-more As of Companion 0.6.0, there will be a companionConfig.json  file in the Atlassian Companion/resources directory.  Could you please verify the contents of this file?   For the MSI install, this file should contain the following: { "builtWith" : "wix" } For the EXE install, the file should contain: { "builtWith" : "squirrel" }   If the config file exists and matches that of what it should be for the MSI install, you will see the following log message: "message" :[ "Application was installed via MSI, not watching for updates" ]  

            Alex K added a comment -

            remus.jivcu

            This is expected behaviour for Companion installed via EXE. Companion App was built with auto-updating functionality. We subsequently released an MSI for enterprise customers. Companion installed via MSI does not have the ability to auto update. This bug was raised because Companion installed via MSI was going down the auto-update code path and failing. The expected behaviour is that Companion installed via MSI will not go down this code path. 

            Therefore, the bug has been fixed only for the MSI installer. The bug itself was not visible to end users, the effect was just spamming the logs with an error message (there was no negative consequence to this). 

            Alex K added a comment - remus.jivcu This is expected behaviour for Companion installed via EXE. Companion App was built with auto-updating functionality. We subsequently released an MSI for enterprise customers. Companion installed via MSI does  not  have the ability to auto update. This bug was raised because Companion installed via MSI was going down the auto-update code path and failing. The expected behaviour is that Companion installed via MSI will not go down this code path.  Therefore, the bug has been fixed only for the MSI installer. The bug itself was not visible to end users, the effect was just spamming the logs with an error message (there was no negative consequence to this). 

            Alexander Greig-More added a comment -

            I have Atlassian Companion v 0.6.0 installed via the MSI and I'm still seeing the following errors over and over:

            ["update error",{"message":"Command failed:....System.Net.WebException: The remote name could not be resolved: 'update-nucleus.atlassian.com'\r\n....

            Can this issue please be opened again? We control software updates with testing so can't allow apps to update themselves automatically. 

            Alexander Greig-More added a comment - I have Atlassian Companion v 0.6.0 installed via the MSI and I'm still seeing the following errors over and over: ["update error",{"message":"Command failed:....System.Net.WebException: The remote name could not be resolved: 'update-nucleus.atlassian.com'\r\n.... Can this issue please be opened again? We control software updates with testing so can't allow apps to update themselves automatically. 

            Deleted Account (Inactive) added a comment -

            I am using Companion 0.6.0 and I can still see the updates check every 5 minutes in the logs. Note that I am not able to use the MSI, it simply does not go through with installation on my Windows 10, so I had to install it via the exe file (see https://confluence.atlassian.com/conf613/edit-files-964960723.html#EditFiles-AtlassianCompanionapp with exe link pointing to https://update-nucleus.atlassian.com/Atlassian-Companion/291cb34fe2296e5fb82b83a04704c9b4/win32/ia32/Atlassian%20Companion-0.6.0%20Setup.exe). If this was fixed only in the 0.6.0 MSI, but not the 0.6.0 EXE installer, then that would be a pity...

            Deleted Account (Inactive) added a comment - I am using Companion 0.6.0 and I can still see the updates check every 5 minutes in the logs. Note that I am not able to use the MSI, it simply does not go through with installation on my Windows 10, so I had to install it via the exe file (see  https://confluence.atlassian.com/conf613/edit-files-964960723.html#EditFiles-AtlassianCompanionapp with exe link pointing to  https://update-nucleus.atlassian.com/Atlassian-Companion/291cb34fe2296e5fb82b83a04704c9b4/win32/ia32/Atlassian%20Companion-0.6.0%20Setup.exe). If this was fixed only in the 0.6.0 MSI, but not the 0.6.0 EXE installer, then that would be a pity...

            Alex K added a comment -

            This has been resolved in Companion 0.6.0. If you have installed Companion via MSI, please upgrade manually. 

            See the release notes here: https://confluence.atlassian.com/doc/atlassian-companion-app-release-notes-958455712.html

            Alex K added a comment - This has been resolved in Companion 0.6.0. If you have installed Companion via MSI, please upgrade manually.  See the release notes here:  https://confluence.atlassian.com/doc/atlassian-companion-app-release-notes-958455712.html

            Jimmy Axenhus added a comment -

            I can confirm seeing this in the log. Would be nice if it could be fixed since the updater is unneeded with the MSI-package.

            Jimmy Axenhus added a comment - I can confirm seeing this in the log. Would be nice if it could be fixed since the updater is unneeded with the MSI-package.

              aknight@atlassian.com Alex K
              nradenovic Nikola
              Votes:
              10 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: