-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Extension and Native App are once again not the same version #632
Comments
I will improve the update checking in the extension in the future to only display the outdated message when the new version is already available on AMO. |
bump I am on zen browser installed the firefox plugin and downloaded the pwa install I get a message that my pwa is outdated?
fresh windows 11 fresh zen browser fresh pwa for firefox install |
the version mismatch should not effect your ability to use firefoxpwa, you'll just get that annoying message in the extension pop up. |
Same issue as #620
It seems that shortly after the 2.13.2 extension update was approved for AMO, the native client extension in the Arch Linux repos was updated to 2.13.3, once again creating a mismatch between extension and native version.
Is it possible to not release the updated native client until the AMO release has been approved by Mozilla so as to avoid this disconnect? It seems like the release to Arch repos is much faster than Mozilla's AMO approval process.
The text was updated successfully, but these errors were encountered: