Trying to update a published app - getting "You must update your item with a crx package."

[Baruchi Har-Lev]

Hello,

When I try to update an extension that I regularly update weekly (manually) in the developer dashboard I am getting the following error

There's no change in the packaging, and it's a minor change in the code (bug fixes)

Couldn't find answers so far. Any idea wha'ts the issue here? 

Best,

Baruchi

[PhistucK]

Try to use a different application to ZIP the extension files, not all of them work, unfortunately.

Try without compression at all (store mode in the various ZIP applications).

Try to extract what you ZIPped to make sure nothing was accidentally filtered.

The most important file is manifest.json, of course, which must be at the root of the ZIP file, not under any folder. Maybe make sure it is in all-lower-case.

☆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/01ddcc7e-0827-4321-954a-38bb31dcadc3n%40chromium.org.

[Baruchi Har-Lev]

Tried a couple of different zip apps, it did not work.

I am using the same zip compressor that I've used for the last 50 times when I've updated the extension.

The manifest is in the zip (and is correct and working)

Any other ideas?

Do you know what the root cause for this message?

Baruchi

[Timebit Admin]

I am having the same issue.  I just uploaded a package that was basically identical the other day with no issues.  

Can you let me know if you found a solution here?

Thanks!

[PhistucK]

Make sure the version is increased in the new package (though that would have probably been a different error message).

Other than that, I have no other ideas... @Simeon Vincent?

☆PhistucK

[Jun Li]

Hi all, any update to the issue? I meet the same issue. Failed to update my package too.

The diffenece from the last successful commit is the manifest version, and some bugfix scripts.

[Simeon Vincent]

I haven't seen this error before. If your haven't already, please open a support request using this form:

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

Simeon - @dotproto
Chrome Extensions DevRel

[Baruchi Har-Lev]

I opened a support ticket 6 days ago. 

Last I heard the team made some changes (code changes I assume), though this still did not fix the issue.

I'll update once I'll hear about a solution

[Joey]

Hi all,

I'm having the same problem. 

zip package is fine and has been uploaded many times before. 

I think it has something to do with the recent Chrome Web Store update. 

Does anyone have a solution?

[Long Dang]

Hi all, any update on the issue? I meet the same issue.
Thanks.

[Baruchi Har-Lev]

According to support this issue should be solved during this week

Best,

Baruchi

[Baruchi Har-Lev]

The issue was resolved by the chrome store team.

I was able to upload my extension.

Best,

Baruchi

[Encore Shao]

Thanks Baruchi for the update!

It looks like it's still not possible to upload my extension, is there some special change with our extension? Or need help from Chrome Team?

[Baruchi Har-Lev]

As far as I understood the change was an internal change in the store API.

If this still persist contact the store support.

Baruchi

[Encore Shao]

Got it, Thanks Baruchi!

Looks like I need to submit a ticket to Google Store.

Encore

[Shiela M Parker]

Shiela M Parker

---

From: chromium-...@chromium.org <chromium-...@chromium.org> on behalf of Encore Shao <encor...@gmail.com>
Sent: Saturday, April 30, 2022 1:37:44 AM
To: Chromium Extensions <chromium-...@chromium.org>
Cc: baru...@gmail.com <baru...@gmail.com>; Encore Shao <encor...@gmail.com>; lon...@cystack.net <lon...@cystack.net>; Joey <j.ko...@gmail.com>; Simeon Vincent <sim...@chromium.org>; Chromium Extensions <chromium-...@chromium.org>; PhistucK <phis...@gmail.com>; ad...@timebit.io <ad...@timebit.io>; lij...@gmail.com <lij...@gmail.com>
Subject: Re: [crx] Trying to update a published app - getting "You must update your item with a crx package."

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/aa6a7208-ff10-4ed6-bec0-a131ff6b983dn%40chromium.org.

[장재영A]

Is there anyone who met this error again?

2hours before, I can upload extension file using webstore api (`https://github.com/fregante/chrome-webstore-upload-cli`). But now, I met error with same action.

You must update your item with a crx package.

33 itemError: [

34 {

35 error_code: 'PKG_MUST_UPDATE_AS_CRX',

36 error_detail: 'You must update your item with a crx package.'

37 }

38 ]

2022년 5월 4일 수요일 오후 7시 6분 15초 UTC+9에 Shiela M Parker님이 작성:

[Zach Warneke]

Hi,

There was a new feature recently launched where, after opting in, your item must be updated using signed CRX packages going forward. Here are some more details about the feature. Is it possible your item was opted in? Maybe by another member if your item is owned by a group publisher?

Zach

[Mulualem Eshetu]

Hi Zach,

Thanks for pointing that out. Yes, I’ve recently been experiencing this issue, and I believe it’s related to the new "Verified CRX Uploads" feature. I was actually the one who opted in, but I’m **not an admin** on our group publisher account.

Given that we’ve decided this extra layer of security isn’t necessary for our current workflow, is there **any way to revert this setting** and go back to the previous upload process using the Web Store API without requiring signed CRX packages?

Would it require an admin to disable it, or is there another way to opt out?

Appreciate your help!

Best,

[Zach Warneke]

Hi,

The setting can only be reverted by reaching out to the Chrome Web Store support team (link). There isn't a predefined option for this, so you'll have to select "Something else" and mention that you'd like to opt out of "Verified CRX Uploads". The support team should then be able to opt out your item within a week or so.

Zach