Inadvertent publish of non-beta

[Don Schmitt]

We inadvertently pushed an update to our "beta" that didn't include the name "beta" but instead had the same manifest (and thus name) as our non-beta listing (although it is unpublished).  Has anyone else made this mistake?

We want to avoid a duplicate listing violation / takedown.  Is there still no way to revert our update before it gets to review?  I sent a message to chrome web store support, any other suggestions?

[Patrick Kettner]

Hey Don!

There is nothing to be concerned with. It should be rejected, but it won't be permanently taken down or anything like that.

Feel free to share the extension IDs and/or support tickets if you would like me to make sure the review team sees your messages.

On Tue, May 21, 2024 at 3:06 PM Don Schmitt <donc...@gmail.com> wrote:

We inadvertently pushed an update to our "beta" that didn't include the name "beta" but instead had the same manifest (and thus name) as our non-beta listing (although it is unpublished).  Has anyone else made this mistake?

We want to avoid a duplicate listing violation / takedown.  Is there still no way to revert our update before it gets to review?  I sent a message to chrome web store support, any other suggestions?

--
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/CAM7AMp%2BZTUqpjpb3VWSvfWmyfWm5WgSsHrBCXY5cy2xBDGK8xg%40mail.gmail.com.