Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update.json not recognised in install directory #603

Closed
2 tasks done
skfin opened this issue Nov 13, 2017 · 4 comments
Closed
2 tasks done

Update.json not recognised in install directory #603

skfin opened this issue Nov 13, 2017 · 4 comments

Comments

@skfin
Copy link

skfin commented Nov 13, 2017

My Setup

  • Operating System: Windows 10
  • App Version: 2.9, 2.10.1
  • I have tested with the latest version
  • I can simulate the issue easily

Description

I'm trying to disable update notifications using the update.json file with:

{ "autoUpdate": false }

This works in the appdata folder but not in the install directory.
I've tried it in both the root folder and resources folder but neither work.

@johnyb0y
Copy link

Same for me. This feature would be great for my deployment. We are using Rocketchat in an virtualized enviroment and users cannot update the client on their own.

@gdelavald
Copy link
Contributor

Thanks for the feedback, it should be an easy fix since we already do that for the servers.json file so if anyone wants to give it a try, PRs welcome.

@krispayne
Copy link

krispayne commented Dec 4, 2019

Can this also be made to work for MacOS? Using #523, #449, #603, and #822 as rough guides, and my own installation, I placed { "autoUpdate": false } in an update-info.json file at ~/Library/Application Support/Rocket.Chat/__update__/update-info.json but was still greeted with an update dialog on first open (to 2.17.0 which does not open on MacOS currently.)

edit:
Looking closer, maybe this needs to just be update.json in the root of ~/Library/Application Support/Rocket.Chat/ ?

edit 2:

That did the trick!

Happy to open another Issue if it's better!

@jeanfbrito
Copy link
Collaborator

Please test if the problem persists with our latest release. I will be closing the issue but if there is any problem yet, we will open it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants