No Feedback When Resending OTP, Leading to Multiple Clicks and Rate Limiting

[zainAwan9175]

Describe the bug

During the appointment process, when users are required to enter their mobile number for OTP verification, clicking the "Resend OTP" button does not provide any visible feedback (such as a success message or error popup). If the OTP fails to send for any reason, the user assumes the button is unresponsive and keeps clicking it multiple times. This can lead to the user exceeding the OTP request limit, causing frustration.

To Reproduce

1. Start the appointment process where a mobile number is required.
2. Enter the mobile number and proceed to receive the OTP.
3. If the OTP is not received, click on the "Resend OTP" button.
4. If the OTP fails to send due to a backend issue, no message is shown to the user.
5. The user repeatedly clicks the button, thinking it is not working, until the rate limit is exceeded.

Expected behavior

1. A success or error message should be displayed when the "Resend OTP" button is clicked.
2. If the OTP request fails, the user should see a notification explaining the issue (e.g., "Failed to resend OTP. Please try again later.").
3. The button should be temporarily disabled with a loading indicator to prevent excessive clicks.

Desktop

OS: Windows
Browser: Chrome
Version: [Specify Chrome version, e.g., 122]

Additional context

@rithviknishad As I am already working on this issue, I am interested in getting assigned this issue to mee.

[Harsh-D-2004]

@rithviknishad can u assign me this

Approach : Show a toast message for the same when it fails to send OTP

But is it already implemented and not working due to OTP API rate limits and using default OTP ??