Subversion Repositories SmartDukaan

Last modification

• Rev 37432 2026-08-27 01:38:10
• Author: amit

• Log message:

  Oppo: reinstall the capture hook after every navigation
  
  Oppo installed the response hook after the first driver.get only. The other
  three navigations -- the "field already filled" reset, the widget-not-found
  reload, and the per-imei reset at the end of the loop -- did not.
  
  Every navigation destroys the JS context, so __oppoCapInstalled, __oppoResp and
  __oppoCaptcha are all wiped and never recreated. Oppo therefore runs blind from
  the second imei of a batch onwards, permanently.
  
  Live evidence from the 00:49-01:03 window after deploying r37431:
  
  Success at attempt 12
  Activation lookup for 1 <- the first imei, right after the initial get
  No getDeviceInfo response 11
  captcha said null on all 11
  
  Both variables null on every miss is the signature: not a failed drag, an
  absent hook. Realme does reinstall at all four of its navigations (r37423) and
  in the same window captured 30 lookups from 30 successes, on the same box with
  the same hook code -- so the hook itself is fine.
  
  Deliberately not touching Oppo's success signal in this change. It still infers
  success from the bar-inform error element being absent, which is the false
  success pattern r37426 replaced for Realme, and it may well need the same
  treatment. But the null hook explains the misses on its own, and changing both
  at once would make the next measurement unattributable.
  
  Not compile-verified: the local build was interrupted. The change is three calls
  to an existing private method in the same class.