Subversion Repositories SmartDukaan

Last modification

• Rev 37434 2026-08-27 05:33:08
• Author: amit

• Log message:

  Oppo: capture the captcha verify separately from the puzzle refetch
  
  Diagnostic only, no behaviour change.
  
  r37433's verdict logging shows all 58 captured oppo captcha responses are
  /api/a (the puzzle fetch) and none are /api/v1 (the verify), while realme shows
  /api/v1 on 20 of 25 failures. The tempting reading is that oppo's drag is never
  submitted for verification at all.
  
  That reading is not safe. __oppoCaptcha is last-captcha-call-wins, and the
  widget refetches a puzzle immediately after a rejected verify. Oppo then waits
  up to 5s for the error element before reading the signal -- ample time for the
  refetch to overwrite the verdict. Realme reads off the lookup response instead,
  which is why its verdict survives.
  
  So "never verified" and "verified, rejected, then overwritten" both fit, and
  they need opposite fixes: the first is a broken gesture, the second is aim.
  
  Keeps the last /api/v1 body in its own variable plus a count, so the failure
  line now reads verifies=N lastVerify=... and the two are distinguishable on the
  next tick.
  
  Ruled out already, so as not to re-chase: drag duration. Time held between
  "Distance is" and "Move click performed" is oppo 1.4s mean / 2s max against
  realme 1.6s / 3s -- effectively identical, so the widget is not abandoning
  oppo's drag for slowness.