extension keeps getting rejected for seemingly the same reason?

Louis Ortiz

unread,

Nov 19, 2023, 10:29:05 AM11/19/23

to Chromium Extensions

We've been trying to publish an extension for the last couple of weeks - and we keep seeing similar rejection reasons, even after working with our dev to get the issues resolved...

Have been hit probably 2-3 times for remote hosted code which we've removed references to - is this typical? Or is there something that we're missing?

Patrick Kettner

unread,

Nov 19, 2023, 10:57:51 AM11/19/23

to Louis Ortiz, Chromium Extensions

Hello Louis,

Have you been in contact One Stop Support? If so, what is your case number?

Additionally, what is your extension ID?

On Sun, Nov 19, 2023 at 7:29 AM Louis Ortiz <louis....@gmail.com> wrote:

We've been trying to publish an extension for the last couple of weeks - and we keep seeing similar rejection reasons, even after working with our dev to get the issues resolved...

Have been hit probably 2-3 times for remote hosted code which we've removed references to - is this typical? Or is there something that we're missing?

--
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/fa23518c-d59e-4990-8929-cd9fedc31b0an%40chromium.org.

Louis Ortiz

unread,

Nov 19, 2023, 4:27:14 PM11/19/23

to Chromium Extensions, Patrick Kettner

We haven't been in touch with the One Stop support yet as we were under the assumption that it was going to be relatively straightforward, our extension ID is: gimdnglebecepanjcmejhlboifkhemih

Patrick Kettner

unread,

Nov 19, 2023, 4:35:18 PM11/19/23

to Louis Ortiz, Chromium Extensions

It is always a good idea to contact OSS to get as much information as possible about your rejection.

In this case, the most recent rejection was because of invalid metadata. Specifically, icon.png that is listed in the `icons` section of your manifest.json was not able to be loaded. I don't have access to the package that was uploaded, so I can't confirm the problem.

Additionally, based on the notes from the earlier rejection it looks like the extension is using Firebase auth. I assume they already have, but it would be worth making sure your developer followed the steps discussed in the github issue to address all of the problems with that as of today.