DevSoftTech Server
82b7b27273
Abha::verifyOtp() and Abha::verifyCommOtp() were overwriting the user-typed, OTP-verified mobile number with whatever the ABDM bridge's verify-otp response echoed back for 'mobile'. Many bridge responses (especially plain mobile-OTP verification, as opposed to Aadhaar eKYC) do not echo the mobile at all, so it silently became empty and was never saved to patient_master.mphone1 during ABHA Register (By ABHA Number / QR / Facility QR / Mobile OTP) or ABHA Create/Verify. Fix: fall back to the originally submitted/verified mobile when the gateway response omits it. Also updated Patient_V.php JS (Verify ABHA tab, ABHA Register Method 1 and Method 4) to resend the mobile number along with the verify_comm_otp call so the server has it available. Address/email are unaffected by this bug: those fields are already mapped via applyAbhaMetaColumns() when present, but the ABDM mobile-OTP verification API generally doesn't return KYC demographic data (that only comes from the Aadhaar-eKYC flow) - so they may legitimately stay blank for phone-based registration methods. |
||
|---|---|---|
| .. | ||
| Authentication/Authenticators | ||
| Commands | ||
| Config | ||
| Controllers | ||
| Database | ||
| Filters | ||
| Helpers | ||
| Language | ||
| Libraries | ||
| Models | ||
| ThirdParty | ||
| Validation | ||
| Views | ||
| .htaccess | ||
| Common.php | ||
| index.html | ||