DEF-001 — Canadian OTP not working (Registration/Login)
DEF-001 — Canadian OTP not working (Registration/Login)
Summary
OTP codes are not being sent/received for any phone numbers during registration and login flows. The developer provided a hardcoded OTP value 1111 as a workaround. This hardcoding blocks proper testing of the OTP feature because there is no way to verify if the OTP generation, delivery, validation, expiry, and security features are implemented correctly.
Environment
- Platform: DriveLink iOS App
- Area: Authentication
- Requirement(s): FR-01, FR-53
- Date Reported: 2025-12-26
- Testing Phase: iOS App Initial Execution (3rd Milestone)
Steps to Reproduce
- Attempt to register or login using any phone number
- Wait for OTP code delivery
- Observe OTP is not received
Expected Behaviour
OTP codes should be generated and delivered via SMS to all phone numbers. The system must send unique, time-limited OTP codes that can be validated during registration and login. Testers must be able to verify the complete OTP flow including delivery, validation, expiry, and resend functionality.
Actual Behaviour
OTP codes are not being sent/received for any phone numbers during registration and login flows. The developer provided a hardcoded OTP value 1111 as a workaround. This hardcoding blocks proper testing of the OTP feature because there is no way to verify if the OTP generation, delivery, validation, expiry, and security features are implemented correctly.
Workaround
Use OTP 1111 (as provided by developer)
Impact
- All users cannot use OTP-based authentication properly
- Cannot properly test OTP implementation, security, and delivery
- Blocks validation of OTP expiry, resend, and rate-limiting features
Severity
High
Status
Pending Retest (as of the February 8, 2026 status report) - Dev Fix Claimed: Yes - Note: Developer claims fixed via Firebase OTP — awaiting verification
Reported By
QA / Testing Team