3

Hello,

It seems that installing extensions from Chrome Store is broken on the latest iPadOS 16 / Orion. The button to add the extension is not active.

I have managed to install the extension from file, but apparently chrome.scripting.registerContentScripts is not working. When I click on the button which has this promise as a handler nothing happens:

https://github.com/zyv/puf-z-eye/blob/fb83a85d95f44398986835e3747b63dc9c7015cf/src/index.js#L17

The rest of the extension seem to work just fine :-/

You can check the extension here:

https://chromewebstore.google.com/detail/puf-z-eye/ohkkeficopcaddmdhbclihnglhbgoboa?hl=en-GB

I wish the API was usable. I find the idea of using Chrome Extensions on iOS really awesome.

1.3.4 (2)

16

    By the way, I have switched to static content scripts, and now the extension seems to work! Wow! It's still a bit stupid that I can't install from Chrome Web Store and have to shuffle CRX files around, but it's great to have it working.

    Also it seems that chrome.runtime.onInstalled.addListener API is silently not supported, but at least it doesn't crash or anything, and if one is using it just for setting default values, it's not great, but OK.

      a year later

      I will mark it as 'Done' because installing the extension works. Not sure about this one specific api though. We hope to improve more extension apis in the future

        Michal hey, that's an interesting take at it 🙂

        The extension in question installs and works, because since I haven't got any reply, I have re-written it to use static content scripts (defined in the manifest) instead of dynamic content scripts (defined programmatically).

        I didn't re-check it now, but if you didn't implement it so far, missing chrome.scripting.registerContentScripts API will cause all extensions using dynamic content scripts to install, but not work, because their content scripts won't be executed.

        If you seriously aim for supporting Chrome extensions, you should consider implementing this API among the first ones to be implemented 🙂

        • Vlad replied to this.

            zaytsev You are right. To be fair you had two bug reports in this thread and one of them is solved. We recommened having only one bug report per thread.

                Vlad ah, alright, so the confusion was caused by my second post.

                No, it isn't solved either, it's just arguably much less critical than the original one. The chrome.runtime.onInstalled.addListener API is used to perform tasks upon the installation of the extensions like setting the default values, and if it's not present, then the extensions might malfunction, but mine isn't affected much.

                    No one is typing