@Vlad good to know. Was it because of the Service Worker like I'd guessed or some other reason? Is there a rough timeline for that release? (not urgent for me, I'm just curious)
In any case, the original suggestion here about displaying more detailed information about why something cannot be installed still stands.
Hi @Vlad, is there any update on this? I am running the latest release of Orion iOS from a last week, 1.2.3, and my extension still shows "Not compatible" instead of an add button, and no further information about why it can't be added. If there's something easy to change in my extension to make it compatible, I'd like to be able to tell what it is so I can do it.
As mentioned above I suspect the reason is that my extension uses an MV3 extension Service Worker. Can you confirm whether or not extension Service Workers are supported yet in Orion iOS (the API list page is not clear on this) and if not whether this would be a reason for an extension to show "Not compatible"?
Thanks and happy new year!
Vlad A screenshot of the "Not compatible" button is in my first reply to you above on December 14. Trying to install from a zip file seems to do nothing. No error, but the extension doesn't appear to be installed. I also tried with a .crx file (not shown in recording) and it's not even selectable in the file picker, it shows greyed out. See screen recording.
I discovered after the screen recording that clicking the "Not compatible" button produces a popover (screenshot) out-of-viewport from the web store saying:
This application is not supported on this computer. Installation has been disabled. The following problems are detected:
- Chrome of version at least 88 is required
My extension's manifest does not specify any minimum browser version, but it does use Manifest Version 3, which was first supported in Chrome 88.
Clicking around on the web store and looking at the manifests of extensions that display "Not compatible" vs those that show the "Add to Orion" button, I found that every MV3 extension I could find is "Not compatible", as well as at least one MV2 extension (though that MV2 extension has a min_chrome_version).
This suggests to me that maybe the issue on Orion side is in injecting its "Add to Orion" button when the Chrome Web Store has already displayed its own Not Compatible button based on minimum_chrome_version or manifest_version fields.
Some examples of extensions that show "Not compatible":
min_chrome_version: 100)min_chrome_version; has a ServiceWorker), Calendly (no min_chrome_vresion; has a ServiceWorker), Dropbox Passwords (min_chrome_version: 99; has a ServiceWorker), Workona Tab Manager (min_chrome_version: 89; has a ServiceWorker), Boomerang for Gmail (no min_chrome_version; has a ServiceWorker), OpenDyslexic (no min_chrome_version; has a ServiceWorker)OK looks like we need to check the minimum chrome version requirement for these and our user agent so we can properly inject add to orion button. Thanks for your debugging work.
Hi, any updates on this? If I understand the issue correctly, I think it would affect most/all MV3 extensions which are becoming more common since Google is limiting submission of MV2 extensions to their web store.
Just mobile/iOS; I'm able to install my MV3 extension in Orion on macOS.