I am seeking some guidance or visibility on an unexpected permanent block my new extension just received.
My extension, Contractless Wallet (ID: 3048079), was flagged and blocked under the Acceptable Use Policy for being “Deceptive or misleading.” However, this happened while I was actively in the middle of the submission process. I was still uploading the src and builder files to the developer dashboard when the submission was locked and rejected and the upload ended up returning a something went wrong style page.
Because the upload was interrupted, an incomplete package was evaluated. The extension is completely legitimate and is a web3 browser based wallet for a blockchain I have developed called Contractless. It contains no misleading or hidden mechanisms, but I wasn’t given the chance to finish uploading the clean source and build scripts to prove it.
I have already submitted an official appeal via the link in the email, but because the extension was completely disabled, I cannot even get a signed .xpi for self-hosting.
Is there an AMO admin who can look into why the review process triggered before the src build file upload process was actually completed? I am happy to provide the full source and build logs to any reviewer.
Thanks for any help or insights you can provide.