Companion update button not appearing

[jaxxzer]

When a user is on a version of companion prior to the latest stable release, an 'update avialable' button should appear on the system page to update the companion software.

This button will only appear if the ROV has a connection to the internet, as indicated on the network page.

First visit the network page to check your internet status. Then, visit the system page to see if the update available button appears. If the button does not appear, try to refresh the page, then wait 10 seconds for the button to appear. If you still do not see the button, please, download a companion system log (using the button at the bottom of the system page and share it here or in the discussion here: https://discuss.bluerobotics.com/t/no-companion-update-button-available/4061

This might be related to #247

[jaxxzer]

If you continue to experience issues with this, and you need to update to 0.0.17, you will need to remove the sd card from the RASPBERRY PI inside of the ROV, and perform the companion installation instructions.

[Williangalvani]

relevant log section from a user (from from https://discuss.bluerobotics.com/t/software-updates-april-2020/7234/21)

2020-04-29T18:54:41+0000 index.js:1336 (Socket.) get companion latest
2020-04-29T18:54:41+0000 index.js:1390 (Socket.) get ardusub version
2020-04-29T18:54:41+0000 index.js:1328 () null0.0.18

2020-04-29T18:54:42+0000 index.js:1338 () nullerror: tag ‘stable’ not found.
error: unable to resolve reference refs/tags/stable: Invalid argument
From https://github.com/bluerobotics/companion
! [new tag] stable -> stable (unable to update local ref)
warning: ignoring broken ref refs/tags/stable.
fatal: ambiguous argument ‘HEAD…refs/tags/stable’: unknown revision or path not in the working tree.
Use ‘–’ to separate paths from revisions, like this:
‘git […] – […]’

[jaxxzer]

@Williangalvani the user was on 0.0.18: https://github.com/bluerobotics/companion/blob/0.0.18/br-webui/index.js#L1337

there's some potential solutions proposed here, but the root of the issue remains unclear to me.

[jaxxzer]

There is some better information on the problem here, and I can think of two possibilities:

• There is an issue with the stable tag moving in the remote repository, and the local ref becomes desynchronized.
• The power was removed from the computer while it was writing to /refs/tags/stable, and the file is corrupt. I think this situation is more likely as git tag -d stable is failing with error: tag ‘stable’ not found.