Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix your chrome or firefox mv3 extension and package it for release
Onur E.
About this gig
Have an existing Manifest V3 extension that is almost ready but still has one focused bug, small behavior change, or release-packaging problem?
I will work on one clearly defined issue in your existing Chrome or Firefox desktop extension, verify the agreed behavior, and prepare the release files included in your package.
Depending on the package, delivery may include:
- Source-code changes and targeted tests
- Chrome or Firefox release ZIP
- Manifest and permission review
- Store title, summary, description, and reviewer notes
- Privacy and data-use declaration draft
- Reproducible source/reviewer archive
- A practical submission checklist
"Store-ready" means the files are prepared and checked against the agreed technical scope. I do not access your developer account, upload or submit on your behalf, or guarantee store approval.
I use AI-assisted tools for analysis, code review, test drafting, and documentation. Every order is customized, reviewed against the source, tested with the reported checks, and delivered under my responsibility. I do not deliver raw generic AI output.
This is an asynchronous, fixed-scope service: no meetings, account access, or ongoing support contract.
Get to know Onur E.
Onur E.
Browser Extension Developer
- FromTurkey
- Member sinceApr 2022
- Avg. response time1 hour
Languages
Turkish, English
I fix and package browser extensions.
I work on existing Chrome and Firefox Manifest V3 extensions: one defined bug or a small, scoped change - verified against your written acceptance criteria and delivered with release ZIP, manifest and permission review, store text, privacy declaration draft, and a reproducible reviewer source archive.
Fixed scope, asynchronous, no meetings. I do not access developer accounts, upload or submit on your behalf, or promise store approval.
I use AI-assisted tools for analysis and documentation; every delivery is customized and checked against your code.
My Portfolio
FAQ
What counts as a small bug or feature?
One existing user flow with a clear expected result and no new backend, authentication, payment, database, or major architecture change. A small feature has no more than three closely related acceptance criteria.
What does store-ready mean?
The release ZIP, manifest, permissions, agreed checks, and package-specific store documents are prepared. It does not mean signed, submitted, published, or guaranteed to pass review.
Will you publish the extension for me?
No. I do not log into developer accounts, accept agreements, pay fees, upload packages, or press submission buttons.
Do you guarantee approval?
No. Chrome and Mozilla control validation and reviewer decisions. An included revision can address a reviewer issue only when it is directly within the original written scope.
Do you use AI?
Yes, for assisted analysis, review, testing, and documentation. The final work is customized and verified. Contact me before ordering if your code-handling policy prohibits this.
Do you need credentials?
No. Never send passwords, tokens, MFA codes, payment details, customer data, or private keys.
