Extensions that were signed after November 10th and before November 18th were incorrectly signed, which would lead to the error you see. If this is your case, you’ll need to submit a new version of your add-on or wait until we automatically sign the incorrectly-signed files again (should happen in the coming couple of weeks).