For the past 6 years, I’ve been uploading my self-hosted add-on for code signing, and I’ve always received automatic validation very quickly, typically within minutes. For some reason, however, my latest version hasn’t received automatic validation. It’s been “Awaiting Review” since Saturday. I uploaded another new version on Sunday, and it’s also “Awaiting Review”. My add-on doesn’t use minification or anything like that, so why is automatic validation suddenly unavailable?
I wasn’t expecting a delay, given my previous 6 years of experience, and the delay is problematic because my multi-browser extension app is actually distributed via the Mac App Store, so I have to wait until the Firefox add-on is approved before I can submit it to Apple for yet another review.
The only change I can think of is that I disabled and deleted an undistributed version of my add-on shortly before uploading the latest version. Could that have somehow flagged my account for manual review?
Hey @StopTheMadness. I don’t expect that disabling/deleting a version would cause this, but the content uploaded for that version might. I verified that your latest submission is pending review and appears to be progressing through the queue normally. I don’t have an estimated timeline for you, but a few other posts in this category seem to suggest the queue is over a week at this point.
I don’t expect that disabling/deleting a version would cause this, but the content uploaded for that version might.
I discovered at the last minute that Mozilla forbids JavaScript code obfuscation, which is why I had to cancel that submission, revert all of my git commits, and upload a new version without obfuscation. The version now awaiting review has no obfuscation and no minimization, as before.
I verified that your latest submission is pending review and appears to be progressing through the queue normally. I don’t have an estimated timeline for you, but a few other posts in this category seem to suggest the queue is over a week at this point.
Ugh, that’s awful. I don’t know that my Safari extension update can wait that long, even though this is extremely unfortunate timing, and the Firefox add-on itself has an important bug fix. But Firefox is only a small percentage of my user base. Can’t my account just be unflagged? Again, the obfuscated version was cancelled within minutes after upload, as soon as I got to the next screen and saw that there couldn’t be obfuscated code. I don’t think I should be “punished” for that.