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

"This item is not compatible with your current Chrome version" #1889

Open
KaKi87 opened this issue Jan 15, 2025 · 18 comments
Open

"This item is not compatible with your current Chrome version" #1889

KaKi87 opened this issue Jan 15, 2025 · 18 comments

Comments

@KaKi87
Copy link

KaKi87 commented Jan 15, 2025

Description

  1. Try installing from Stylus - Chrome Web Store on the latest version of Kiwi Browser for Android
  2. See incompatibility error message and greyed out install button
  3. Try installing from the ZIP at Release v2.3.6 · openstyles/stylus
  4. See it working perfectly even though deemed incompatible

System Information

  • OS: Android 14
  • Browser: Kiwi Browser 124.0.6327.4
  • Stylus Version: 2.3.6

Screenshots, links, CSS


Thanks

@KaKi87 KaKi87 added the bug label Jan 15, 2025
@tophf
Copy link
Member

tophf commented Jan 15, 2025

The ManifestV3 version of Stylus requires Chromium 128 or newer. For now, you can install the ManifestV2 version manually as an unpacked extension from our releases page. It won't auto-update, but you can subscribe to new releases by clicking the Watch button in the project page here on github, then you'll update the extension manually upon a notification, which is actually safer because you can make a backup prior to the update.

Chromium 128 is required because it implements support for headers in declarativeNetRequest, which is necessary for the installer and "instant inject" option. Lowering the minimum version requirement is possible and I already thought about it. The user would have to enable webRequestBlocking via a policy or a command line switch though, which might be impossible for an Android app, unless it allows the user to add the command line switches somewhere in its UI. Without webRequestBlocking, only the installer option can be salvaged by introducing an asynchronous listener that redirects matching URLs to our installer UI.

Lowering it to Chromium 123 is possible. It's the first version that implements SW static routing that we use to make own pages of the extension open as quickly as in ManifestV2.

Lowering it to Chromium 116 to support Kiwi 124 would introduce a flicker of empty content when opening own pages, but we can "hide" it by adding a fade-in reveal, which is a common deception e.g. Chromium's own newtab page does it.

@KaKi87
Copy link
Author

KaKi87 commented Jan 16, 2025

I would appreciate lowering the version requirement so that automated updates would work from the Chrome store.

However, an alternative option could be to build a CRX into GitHub releases and add an XML file into the repo to allow automated updates out of store : https://developer.chrome.com/apps/autoupdate#update_url

Thank you

@tophf
Copy link
Member

tophf commented Jan 16, 2025

Can't promise I'll work on it anytime soon given the fact there is a workaround and personally I'm against auto-updating programs/extensions, 99% of stuff I use I update manually when notified, including Chrome (via local policies).

@KaKi87
Copy link
Author

KaKi87 commented Jan 17, 2025

So, as a developer maintaining Stylus, you don't believe that your users should have your updates installed automatically ?

@tophf
Copy link
Member

tophf commented Jan 17, 2025

It would be hypocritical if I did. As a programmer I know that programs should never be trusted implicitly, by default.

@jesus2099
Copy link

jesus2099 commented Feb 5, 2025

I have Kiwi Browser 132.0.6961.0, which is said to be the final version. *

I have Stylus 2.3.10.

Now, with this new Kiwi version, it often happens that Stylus does not achieve to fully load (no userstyle and Stylus extension management window not loading, not reachable).

I force close Kiwi browser and reopen, and then it's fixed.


* This version has some CSS bugs strangely, in some sites.

@tophf
Copy link
Member

tophf commented Feb 5, 2025

Try using the mv2 version.

@jesus2099
Copy link

I'm against auto-updating programs/extensions, 99% of stuff I use I update manually when notified

And maybe what @KaKi87 was asking for, would also have allowed being notified, instead of not? 😉

@tophf
Copy link
Member

tophf commented Feb 5, 2025

I don't understand, please rephrase.

@jesus2099
Copy link

Thanks for the MV2 version hint, I didn't know it existed.

I can still restart Kiwi, at the moment, when it happens.

And anyway, my primary focus now is to find a good replacement Android browser with Violentmonkey and Stylus support (and webdev tools, and Copy link text).

@KaKi87
Copy link
Author

KaKi87 commented Feb 7, 2025

I don't understand

Me neither, but here's a guess : maybe they're asking for the ability to get notified when a new release is published, and provide a button to download a CRX.

That said, not offering automated updates on browsers is annoying, because there are more steps than even installing software on the worst OS (Windows) : downloading, going to extensions, navigating to the downloaded file and selecting it.

Thanks

@tophf
Copy link
Member

tophf commented Feb 7, 2025

you can subscribe to new releases by clicking the Watch button in the project page here on github

@KaKi87
Copy link
Author

KaKi87 commented Feb 7, 2025

That's even less practical.

@tophf
Copy link
Member

tophf commented Feb 7, 2025

Why? It's a release notification.

@KaKi87
Copy link
Author

KaKi87 commented Feb 7, 2025

That doesn't even provide a one-click download to the right file, so it's even more steps having to use GitHub notifications while it's already more steps having to deal with browser settings menus.

@tophf
Copy link
Member

tophf commented Feb 7, 2025

A couple more seconds isn't a problem. One shouldn't update software without looking at what's changed anyway.

@jesus2099
Copy link

jesus2099 commented Feb 8, 2025

I have uninstalled normal version 2.3.10 (that doesn't always run properly on Kiwi 132), and installed MV2 versions zip manually.
But this one never runs ok:

Unrecognized manifest key 'browser_specific_settings'.
The 'match_origin_as_fallback' property is restricted to extensions with 'manifest_version' set to 3 or higher.

Update

No no, sorry, there are these errors in the Extension tab, but Stylus MV2 actually runs perfectly!

@tophf
Copy link
Member

tophf commented Feb 9, 2025

Yep, those are just warnings in an older Chromium. The first one has no impact at all, the second one means that this version of Chromium can't style some of iframes (IIRC those with sandbox attribute).

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

3 participants