Hello Chrome Extensions team,
I’m looking for clarification on a Chrome Web Store lifecycle/enforcement state that we are currently unable to resolve through the normal support channel.
Our extension, UNOLO Wallet, has never been publicly published on the Chrome Web Store. Its initial submission was rejected during pre-publication review.
Since that rejection, we have performed substantial remediation and uploaded a new revision, v1.0.3, to the same existing item.
The Developer Dashboard successfully accepts the new package and allows us to update the Store Listing, Privacy declarations, permission justifications, and save the new draft.
However, when attempting to submit this remediated draft for review, the Dashboard reports:
“This item currently cannot be resubmitted because of an unrectifiable violation. If you believe this enforcement decision was made in error, you may only appeal. If the appeal is approved, the block will automatically be removed and you may resubmit.”
This is the part we are trying to understand.
We are not asking for the previously rejected revision to be reinstated, and we are not attempting to bypass the enforcement by creating another item.
We are trying to determine the correct procedure for allowing the new remediated revision to enter review.
The current state is:
Could someone familiar with CWS moderation clarify:
Does the prior enforcement have to be manually cleared before a new remediated revision can enter review?
And if so, what is the correct escalation path when the normal support/appeal responses address reinstatement of the prior revision rather than submission of the new remediated draft?
We would greatly appreciate clarification on the intended lifecycle here.
Thank you.