Publishing

My extension submission was rejected

If your extension submission was rejected, you probably got an email with the reason. You'll need to fix the issues and upload a new build of your extension to the store and send it for review again.

Make sure to follow the guidelines when submitting your extension to ensure that everything is setup correctly.

Version number mismatch

If you get version number conflicts when submitting:

1. Ensure your manifest.json version matches what's in the store
2. Increment the version number appropriately for each new submission
3. Make sure the version follows semantic versioning (e.g., 1.0.1)

Missing permissions in manifest

If your extension is rejected due to permission issues:

1. Review the permissions declared in your manifest.json
2. Ensure all permissions are properly justified in your submission
3. Remove any unused permissions that aren't essential
4. Consider using optional permissions where possible

Learn more about permissions

Content Security Policy (CSP) violations

If your extension is rejected due to CSP issues:

1. Check your manifest's content_security_policy field
2. Ensure all external resources are properly whitelisted
3. Remove any unsafe inline scripts or eval usage
4. Use more secure alternatives like browser.scripting.executeScript