phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Need Chrome Extension Developer for Bug Fixing & Request Handlin

  • Posted:
  • Proposals: 22
  • Remote
  • #4494062
  • Open for Proposals
Isha S.Vishal W.Huzaifa A.Priyanka K.Christopher A. + 17 others have already sent a proposal.
  • 1

Description

Experience Level: Entry
Estimated project duration: less than 1 week
I need an experienced Chrome Extension developer to debug and fix some issues in my existing extension.

Current issues:

* Some requests are failing
* Required IDs/data are not getting detected properly
* Extension flow works inconsistently
* Need better request/session handling
* Need debugging for content script and service worker communication

Requirements:

* Strong knowledge of Chrome Extensions (Manifest V3)
* JavaScript experience
* Service workers
* Network/API debugging
* Request handling and extension optimization

I already have:

* Existing working files
* Error logs
* Screenshots
* Different extension versions for comparison

Need someone who can analyze the issue and fix the extension properly.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Sudhanshu K.

    Hi, thanks for the detailed breakdown. To diagnose the issues properly, could you clarify: whether the failing requests are related to CORS/authentication/rate limits, if the extension communicates with any external APIs or authenticated sessions, and whether the inconsistencies started after moving to Manifest V3/service worker architecture or were present before as well?

    Keshav H.An hour ago

    From my latest testing, the issue appears to be mainly related to rate limiting and request/session behavior.

    The automated flow starts receiving 429 “Too Many Requests” responses, and instead of JSON the server returns an HTML warning/block page. This causes JSON parsing errors like:

    “Unexpected token '<' ... is not valid JSON”

    The manual browser flow still works normally, but repeated automated requests eventually trigger a temporary calendar access restriction.

    The extension currently uses authenticated sessions with dynamic cookies/tokens, and most logic is running through the Manifest V3 service worker flow.