search

Shared-Reality-Lab / IMAGE-browser

IMAGE project browser extensions & client-side code
Other
2 stars 0 forks source link

Verify browser extension manifest V3 compliance #367

Closed jeffbl closed 8 months ago

jeffbl commented 10 months ago

received an email from Google indicating that our account still has Manifest V2 extensions published. We don't have any non-IMAGE extensions to my knowledge, so this implies that we haven't done some step that makes us fully V3 compliant.

To: sharedrealitylab@gmail.com You still have one or more published extensions currently running on Manifest Version 2, which has been deprecated. We recently announced the updated phase-out timeline of Manifest V2, and your item(s) will be impacted by these changes. More specifically, if you have not migrated to Manifest V3 by June 2024, your Manifest V2 extension may begin to be disabled on Chrome browsers ...

Need to verify both the production and test extensions are fully Manifest V3 compliant. Don't know how that could not be the case given manifest.json specifically says V3:

https://github.com/Shared-Reality-Lab/IMAGE-browser/blob/b4789596d5deda026a789eb0b1621ac2f8a43194/src/manifest.json#L2

@Cybernide if you have access to the google account and can see all our extensions listed, is there any further indication of what might not be in compliance? If you could check, then assign to @jaydeepsingh25 with any relevant information, hopefully we find this is just a spurious notification or applies to an old extension or something, but best to be sure so we don't break in June 2024.

Cybernide commented 9 months ago

There's nothing obvious on the dashboard and no further emails indicating what the issue could be. Suggestions for next steps?

Cybernide commented 9 months ago

Did some Googling but the only documentation I could find were: https://developer.chrome.com/docs/webstore/troubleshooting#additional-requirements-for-manifest-v3 https://developer.chrome.com/docs/extensions/develop/migrate/checklist

jeffbl commented 9 months ago

@jaydeep I poked around a bit and don't see any clear issue, but I'm not familiar with this. There is not a huge rush since this won't cause problems until June, but we don't want any nasty surprises then. Can you please skim through the links Cyan listed above to see if anything looks suspicious for us? If not, we can reach out to web store support via this link:

https://support.google.com/chrome_webstore/contact/one_stop_support

We can ask for clarification of which extension is at issue, and what the issue is, given that the only ones listed there are already marked V3? I looked a bit to see if there is some kind of Manifest V3 validator, but indications seem to be that if you tag it V3 in the manifest, anything breaking should cause an error, so I'm not sure how we would know what the issue is.

jaydeepsingh25 commented 8 months ago

Received confirmation from Google, extension is v3 compatible and no further action is required. Hence closing the issue.