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: 29
  • Remote
  • #4494062
  • Expired
Isha S.Vishal W.Huzaifa A.Priyanka K.Christopher A. + 24 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

  • Shobi K.


    Before moving forward, I would like to ask a few important questions:
    * Are the failed requests related to external APIs, authentication sessions, or page scraping?
    * Is the extension issue happening on all websites or only on specific domains/pages?
    * Do you already know which extension version was last fully stable for comparison?

  • 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.08 May 2026

    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.

    Sudhanshu K.14 May 2026

    Thanks for the clarification, that helps narrow things down a lot.

    It sounds like the main issue is around how the extension is handling authenticated requests and session persistence under MV3, especially once rate limiting and temporary blocking start happening. I’d want to review:

    * how requests are currently queued/throttled
    * service worker lifecycle + session/token refresh handling
    * cookie/auth propagation between content scripts and the service worker
    * retry/backoff logic after 429 responses
    * detection of non-JSON/block responses before parsing
    * whether parallel/background requests are unintentionally triggering anti-bot protections

    I’d also compare the working/manual browser flow against the automated extension flow to identify what request patterns are causing the restriction.

    Could you also share:
    * whether requests are being made via fetch from the service worker or injected page context
    * approximate request volume/frequency before blocks occur
    * whether the target platform uses Cloudflare or similar bot protection?