-
Notifications
You must be signed in to change notification settings - Fork 466
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
Forced updates mean I must re-downgrade after every launch #924
Comments
First of all thank you for highlighting this, this slipped through on my end. I have now added it as a note to the release |
To head off one possible suggestion of possible workaround... Previous suggestions of Flathub and HomeBrew don't work because Flathub is for Linux, and both of these have already bumped to I have long used MacPorts, so I tried to install the |
Please stop posting the same issue over and over again. You are using an operating system that has been without any support from Apple for over 2 years now, that includes security updates. We cannot support your use case. |
@saghul — I am currently trapped on macOS 10.14 due to mission critical abandonware, which breaks with the update to macOS 10.15. I would LOVE to upgrade, I assure you, but I cannot. I have found and hereby offer a workaround for the worst Jitsi pain, for others who may run into this issue: install Little Snitch, and when it alerts that Jitsi Meet.app wants to connect to |
That can work. Now that we reached the point of no return you could just make a custom frozen in time build for yourself too. |
I'd love to know how to do that. At first blush, it seems I would need to disable the phone-home code somehow, in addition to running whatever compiler, etc., (all of which I have installed, just minimally used)... At this point, I'm little more than a script kiddie. My primary coding language is English, though I have ever debugged a little Pascal and a little C and even written some AppleScript and |
You can follow these steps: https://github.com/jitsi/jitsi-meet-electron#building-the-production-distribution |
Note that that anchor is hidden by default. Readers must expand the Show building instructions section. Then, the "first step" is not documented beyond "Install Node.js 16 first", which I think would benefit by at least a link to relevant instructions from that crew. I did Google that f'ing thing, and that got me to nodejs.org where I found that Node.js 16 is on its last last last legs. Still, I downloaded and installed the relevant All that said, if I had reached the point of building the production distribution — so far as I can see, I would have exactly the same issue of auto-updates as I have with the prebuilt download. I think I am best off living with blocking Jisti Meet.app's access to |
Oh right I forgot the most important part 🤦 Edit package.json and drop the project URL. That is what is used for checking for updates. |
I wonder whether |
We don't use that file ourselves AFAIK. The update URL gets bundled with the app and it's taken from package.json. Since you will essentially be keeping a fork, edit the file, remove the URL and the build won't self-update. |
Description
Version 2023.11.0 reports "You have macOS 10.14.6. The application requires macOS 10.15 or later."
Manually downgrading to 2023.10.0 works fine for the duration of that launch. But upon quit, it forces update to 2023.11.0, which will report "You have macOS 10.14.6. The application requires macOS 10.15 or later." at next launch.
Related to this, "What's Changed" should include "no longer compatible with macOS 10.14.x or earlier."
Current behavior
Manual downgrade to 2023.10.0 is required after quit, which forces update to 2023.11.0.
Expected Behavior
Announce that 2023.11.0 is available, and prompt me to install if I want to, and optimally warn that the new version won't run on my version of macOS, so I shouldn't update Jisti Meet.app unless I also update macOS.
Possible Solution
Revert from forced app update to manual updates.
Steps to reproduce
Should be obvious
Environment details
macOS Mojave 10.14.6 (18G9323)
Other notes
I am sure I am not the only person impacted by this. Unfortunately, there's no good way of learning how many others are impacted aside from posting here, and even then, it's not at all guaranteed that others will notice and/or chime in. Equally unfortunately, I participate in working groups which ditched Zoom and WebEx and others because they are not open source, in favor of Jitsi primarily because of its open source nature, so I have no choice but to use it. This is in many ways a replay of #686 and #676, but I remain hopeful that there will be a change in response.
The text was updated successfully, but these errors were encountered: