Subversion Repositories SmartDukaan

Last modification

• Rev 37423 2026-08-26 18:59:28
• Author: amit

• Log message:

  Realme warranty check: retarget the rebuilt page and read its JSON
  
  Realme has recorded nothing since 24-Aug, the same day Oppo stopped. Driving the
  page confirms why: it was rebuilt and every selector the code used is gone.
  
  .sn-input -> the field is now .imei-input input (placeholder 'Please input IMEI')
  div.check-btn -> the submit is now an icon, .imei-input .search-icon
  
  So it failed even earlier than Oppo did -- it could not type the imei, let alone
  reach the captcha, which is why the log showed only 'Initiating webdriver...'.
  
  The result now comes from the JSON the page already receives
  (customer-api.realme.com/in/active/check) rather than an XPath keyed off a label
  that no longer exists. That old locator also had an '| //h1[contains(@class,
  title)]' branch which would silently match a page heading and try to parse it as
  a date. The API is explicit: expiryDate (yyyy.MM.dd) and an isActivation flag,
  so nothing is inferred from message text.
  
  expiryDate is the WARRANTY EXPIRY, so a year is still subtracted -- warranty is
  12 months as standard. Checked against our own records rather than assumed:
  41,267 of 41,289 stored Realme activation dates precede the date we checked
  them, averaging 13 days before, which is only consistent with the subtraction
  already being correct.
  
  Ports the r37422 captcha fix verbatim -- identical dingxiang slider, identical
  15px calibration nudge that made it land ~30px out against a ~30px hole. And as
  with Oppo the outcome is always recorded, even as null: findElement THREW when
  the element was missing, so nothing was written and the imei was re-queued every
  5 minutes indefinitely.
  
  Also converts 29 System.out.println to the logger. The cron JVM's stdout is a
  socket from the launching ssh session, so every diagnostic was going nowhere.