Subversion Repositories SmartDukaan

Last modification

• Rev 37431 2026-08-27 00:33:09
• Author: amit

• Log message:

  Realme/Oppo: capture the lookup off Response.prototype, not window.fetch
  
  Realme solves its captcha well -- the widget's own verify endpoint says
  success:true on 526 of 829 attempts, 63% -- and records nothing. Every one of
  those solved captchas is logged as "Failed" and the imei re-queued.
  
  The lookup is not missing, it is invisible. realme's client calls Nuxt's $fetch
  (ofetch), which takes its reference to globalThis.fetch when its bundle is
  evaluated. That happens before driver.get() returns, so by the time
  installResponseCapture wraps window.fetch the client is already holding the
  original. r37425 added that wrapper and could never have worked.
  
  Verified on the live page: the same $fetch request is invisible to a
  window.fetch wrapper and visible to a Response.prototype one.
  
  Response.prototype.json/.text are resolved per call, so patching them catches
  any client whenever it took its fetch reference -- the same reason the
  XMLHttpRequest.prototype.open patch has always worked (it is how the captcha
  verdict gets captured today).
  
  The clone is read with the ORIGINAL reader. Calling the patched one recurses
  forever and hangs the page; that is not theoretical, it hung a test run.
  
  Applied to Oppo as well. Its XHR path works today (673 lookups, 0 missed), so
  this is defence against the same trap following any migration -- which is what
  r37425 was reaching for and did not achieve.
  
  Expected: Realme goes from 0 rows to roughly its captcha rate. Unchanged:
  59% of attempts still never find the circles, same ceiling as Oppo.