Google not allowing to upload manifest v2 plugin (trying to upgrade plugin not a new upload)

[Amit Harlikar]

As per google documentation https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/ V2 versions are allowed till 2024 to upgrade (we are not uploading new extension, upgrading existing version with some bug fixes) but after bug fixing when we tried to upgrade plugin we are getting error to update extension to V3 (manifest).

Can someone provide guidance on how to upload V2 extension and skip V3 error.

I tried to upgrade extension to V3 also but service worker creating problem in DOM as its not having access to DOM so we wanted to continue with V2 only for now by making fixes in existing extension.

[PhistucK]

I have not tried updating my extensions for a long time, but just make sure you have nothing in the manifest that happens to be version 3 specific.

Also, not sure whether you can return to 2 if you already uploaded a package with 3 once (just in case you did).

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ce127c1b-cbce-4744-8c9d-a8e180f8b9f6n%40chromium.org.

[Amit Harlikar]

no we tried to do that but upload not succeed as service worker not able to get DOM ( as service worker don't have access to DOM)

[Erek Speed]

Can you take a screenshot of the error? When does it appear exactly? I update an MV2 extension weekly (via the REST API) and haven't seen any errors.

2022年11月29日(火) 23:57 'Amit Harlikar' via Chromium Extensions <chromium-...@chromium.org>:

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/74d6eca4-c84b-4d49-ae59-4b971a2a171an%40chromium.org.

[Amit Harlikar]

PFA

[Amit Harlikar]

it all started with error-

There was a problem uploading your file. Please try again. * key field is not allowed in manifest.

then when we tried removing key field in manifest and upload, it started to ask permission justification (may be by considering V3 manifest)

[Robbi]

From the error message it would appear that you are trying to upload a new extension (instead of updating an existing one).

Permission justifications might be normal if it's been a long time since you updated the extension.

[Deco]

You have interpreted the timeline incorrectly. 

Support for Manifest V3 in regards to legacy Manifest V2 extensions with upload is strictly with enterprise applications - you are not using this, so you cannot upload updates to it.

Support ended in June for allowing further packages to be submitted to the CWS on MV2, so you will need to update the package locally to MV3 before you can update it on the CWS.

Thanks,

Deco

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/17dff7d8-9913-4bd8-b11a-5b7eeeecade4n%40chromium.org.

[Amit Harlikar]

Hi Deco,

 I am doing this for enterprise application only, aftter June also twice i am able to update extension, but facing issue now only. I just retied also giving error as "key field is not allowed in manifest".

after removing key field from manifest its forcing to migrate to V3 

[Deco]

Ah, there was a prior comment however it's worth mentioning that the CWS uses the MV as it's method of detecting an update, as you tried MV3, it's assuming updates from then on will be MV3, it isn't possible to reverse back to MV2 due to this.

Cheers,

Deco

[Amit Harlikar]

We tried update with MV 2, it was giving error to upgrade to MV 3, we were not having option than making changes in manifest to go for version 3. We able to make code changes to go for MV 3 (minimum code changes) but background is now service worker which is not having DOM access, this is creating problem for us and forcing to make big code changes. Is there any way we can send DOM in service worker and keep service worker alive till all code gets executed?

[Amit Harlikar]

https://stackoverflow.com/questions/21497781/how-to-change-chrome-packaged-app-id-or-why-do-we-need-key-field-in-the-manifest

here is one link which i was trying today also but not succeed. in above link someone posted like if you are having problem with key try removing existing uploaded plugin and upload new one. we don't want to try this option as if we delete existing one and not able to upload new one then its like our customer need to wait till we are upgrading to MV 3