Rejection - Red Potassium - Wallet functionality

[Ed Burnette]

I've been trying to get an extension approved since October 8th, but it keeps getting rejected with the following reason:

Violation(s):

Inaccurate Description - Missing info:

• Violation reference ID: Red Potassium

• Violation: Item's description does not mention the following functionality:

  • Wallet functionality

• How to rectify: Update your item's description to describe all functionality or remove the corresponding source code from the package

• Relevant section of the program policy:

  • If any of your Product's content, title, icon, description or screenshots contains false or misleading information, we may remove it. (learn more)

I've escalated it twice. The last one was "1-8064000037526". The response listed two problems:

Inaccurate Description: 

• Violation: Extension provides wallet related code AyraUi.10144c74.js file, which is not the primary functionality of the item.

• How to rectify : Please remove the functions related to the wallet which is unnecessary in the package.

Code Readability Requirements :

• Violation : Extension has obfuscated code in AyraUi.10144c74.js which is present in the code package.

  • Sample Code: function $b4044a8e017d1cf6$var$p(a) {

• Corrective action: Remove all obfuscated code in the extension package. Code should be human readable form.

I'm using Parcel to build the extension, and the .js file is the output from Parcel that bundles all my code together with dependencies.

Regarding wallet functionality, I don't have any. The application listens to the microphone and does transcription and AI - nothing to do with wallets. Also, the extension was accepted once on September 11th and changes since then have been minimal.

Regarding obfuscated code, the code in question comes from the react-dom.production.min.js library. I just tried submitting a debug build that uses a non-minified script, but it was rejected again anyway.

Does anyone have ideas about how to get the extension accepted?

[Patrick Kettner]

Hi Ed,

You can appeal a rejection through One Stop Support (https://support.google.com/chrome_webstore/contact/one_stop_support). If you have done that, can you please share the extension's ID and the case number?

patrick

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/85a11c43-a854-49a6-b9a5-d6b5bc65da91n%40chromium.org.

[Ed Burnette]

ajegioikoifldgjooflfojfnjihbghje ,  1-8064000037526

Since my original posting, I resubmitted the extension, adding the words "and wallet" to the description (even though I did not put a wallet in there), and the submission was accepted. So, I have a workaround, but I'm not happy with it.   

[Cuyler Stuwe]

Is it possible that you're using a compromised third-party dependency that's stealing wallet information?

[Ed Burnette]

I don't think so; my dependencies are pretty standard:

 "dependencies": {
  "@clerk/chrome-extension": "1.1.13",
  "node-fetch": "^3.2.2",
  "prop-types": "^15.8.1",
  "react": "^18.3.1",
  "react-dom": "^18.3.1",
  "react-router-dom": "^6.27.0",
  "ua-parser-js": "^1.0.39"
 },