The Chrome Web Store is hostile to WebAssembly: Google rejected my free extension for not using permissions it uses

Description and use

Google’s review process treats permissions as unused if they are not referenced in JavaScript, leading to rejection of WebAssembly‑based extensions that correctly use those APIs. The developer’s extension was rejected despite functional usage of storage and offscreen permissions.

Problem

Google rejected a free Chrome extension that uses the storage and offscreen permissions because the review process could not detect their usage in WebAssembly code.

Outcome

Google’s review process treats permissions as unused if they are not referenced in JavaScript, leading to rejection of WebAssembly‑based extensions that correctly use those APIs. The developer’s extension was rejected despite functional usage of storage and offscreen permissions.

Workflow

• 1. Submit extension to Chrome Web Store.
• 2. Receive rejection for keyword spam; remove list and resubmit.
• 3. Receive second rejection claiming unused storage and offscreen permissions.
• 4. Provide code snippets, GitHub links, and steps to observe permission usage.
• 5. Receive reply that code cannot be seen and request removal of permissions or proof of breakage.
• 6. Recognize that the review process relies on text search of JavaScript, missing WebAssembly usage.