-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Winget option not working properly. #458
Comments
Because winget packages need to go through PR to get added to their repository, there is some delay between when a new version is released and when it's available in winget. However, 2.10.1 specifically should already be available in the winget repo. You can try updating the source before installing the new package version:
Maybe you can also use:
Which I think automatically updates the source and then upgrades the package. |
Did all those. Still says it's outdated, while no new updates could be found. it's only when i install it manually that the extension removes the "outdated" message. |
I don't know why this happens. The PR to update the winget package (microsoft/winget-pkgs#135747) has been merged two days ago. I also tried to run
There are two separate programs. One is the extension (which is updated automatically by Firefox), and one is for the native connector (which you need to update yourself, either by running the installer, using winget or other package managers). It seems that your extension is already updated to the latest version (2.10.1), while the native connector is still outdated (2.9.1). You can also check which native version do you have with:
That version should match the native version specified on the "about the project" screen in the extension settings. You should also check the installed programs in the Windows Settings or Control Panel if there are multiple PWAsForFirefox entries listed. If the versions don't match or you have multiple entries, maybe you have multiple versions installed at the same time, which may cause problems. But I think that your problem is that winget repository isn't updated for you for some reason. Also, the message in the extension is actually wrong, it should say something like "The native connector is outdated". I will fix this in the future, and it's not the cause of your problem. |
Yeah, as stated in the "Environment" section of the report, the actual version is on 2.10.1, but the "native" version is stuck on 2.9.1, for some reason. The command you stated returns 2.10.1 as well. So winget does get the correct version and it is installed, but the extension doesn't find it and hence return that it's outdated. |
Yeah, then you may have multiple versions installed. One in your custom location, which is the one that the extension detects and is outdated. And another (probably in the default location), which is installed by winget, is up-to-date and in Apparently, winget has support to change the installation directory: microsoft/winget-cli#489 (comment) You can try to uninstall the program both from winget and manually from the control panel, so all versions get removed. You can also manually remove some registry keys and directories, but before removing them, please post here which ones exist and where they point to, so I can know a bit better what exactly might have happened. So, this should clean all registrations for native messaging and any remaining directories (except PWAs and data). After this, you can try to install the package with winget and specify the installation directory:
Hopefully, winget will remember that location and correctly install future upgrades. If that doesn't work, I don't know how to fix this properly. I know that the installer has some problems (see #268), and maybe this is also one of them. But I think that winget also has problems with some installers on their side. |
Alright, that did the trick. Cleared the registry keys and removed both installations (kept just the config file, which held the profiles). The registry keys for both |
I hope it will remain working with future updates. I will now close this issue. If something breaks again, please let me know (although I am not sure what to do in that case). |
Description
Trying to update the extension by doing the winget steps. Terminal says it's installed and cannot find a newer update, but PWA says it's outdated.
This happens everytime the native version gets updated and the only way to fix it is to install it manually, which i'm tired of doing because winget doesnt work.
Steps to Reproduce
Same steps as the winget steps. PWA just not recognising the native version.
Additional Information
I'm not sure if it's relevant, but PWA is not installed in the default location, but on a separate drive.
Environment
The text was updated successfully, but these errors were encountered: