chromestore submission rejected: ’Invalid value for ‘oauth2.client_id’

muly commented 9 months ago

Version: 1.1.1 Status: Rejection Violation date: Dec 21, 2023

Violation type: Spam and Placement in the Store Details:

Violation reference ID: Yellow Magnesium
Violation: Not providing promised functionality
- ’Invalid value for ‘oauth2.client_id’
How to rectify: Test the code that you submit to the web store locally, verify that your submission contains the files you expect at the paths you expect, and is working as intended. For more information, please refer to the documentation and migration checklist on Manifest V3 version.
Relevant section of the program policy: Extensions with broken functionality - such as dead sites or non-functioning features - are not allowed.

muly commented 9 months ago

Resubmitted after adding key to manifest file. retrieved the key from chrome webstore using the below instructions and used that key to generate the zip file and uploaded that zip file and submitted.

go to chrome developer dashboard.
go to Package tab and click View public key

wait for review of the submission.

PR: https://github.com/muly/product-track/pull/64

muly commented 8 months ago

the draft is approved but is failing to download from chrome store. getting below error: Download error: Invalid manifest

chrome store link: https://chromewebstore.google.com/detail/product-track/ichhakcbialminoadfkhalilmdhkmifn

muly commented 8 months ago

it turns out that the above error was misleading. use the below steps to see the correct error:

go to chrome web store developer dashboard
go to product-track
go to Package page
under the Draft or the Published section, click the .crx file link under CRX file column
this should download and attempt to install.
Note: Draft might fail to download, so confirm by clicking Download suspicious file
now you should see the actual error (if any) on the top of the page.
if successful you will see a message Apps. extensions, and user scripts cannot be added from this website

the error shown is as below. Package is invalid. Details: 'Invalid value for 'oauth2.client_id'.'.

so resubmitted the package with the client id for the dev manifest file using the correct client id pulled from the gcp console. wait for review of the submission.

PR https://github.com/muly/product-track/pull/68 is updated to include the client id for dev deployment aswell.

muly commented 8 months ago

the issue is resolved.

muly / product-track

chromestore submission rejected: ’Invalid value for ‘oauth2.client_id’ #63