Bug: Blank toast notification shown when linking ABHA to a patient
Description
When linking an ABHA number to a patient, after OTP verification succeeds and the ABHA is linked, a blank/empty toast notification appears alongside the success toast ("OTP has been verified successfully."). The blank toaster has no message content.
Steps to Reproduce
- Go to a patient's details page
- Initiate ABHA linking flow
- Enter the ABHA number and verify OTP
- After successful OTP verification and ABHA linking, observe the toast notifications
Expected Behavior
Only meaningful toast notifications should appear (e.g. "OTP has been verified successfully."). No blank/empty toasters.
Actual Behavior
A blank green success toast appears with no text content, alongside the actual success message toast. The network tab shows all API calls (verify_otp, link_patient, patient details) returning 200 successfully.
Notes
The blank toast is likely triggered by an API response handler that calls the toast function with an empty or undefined message after one of the linking API calls (verify_otp, link_patient).

Bug: Blank toast notification shown when linking ABHA to a patient
Description
When linking an ABHA number to a patient, after OTP verification succeeds and the ABHA is linked, a blank/empty toast notification appears alongside the success toast ("OTP has been verified successfully."). The blank toaster has no message content.
Steps to Reproduce
Expected Behavior
Only meaningful toast notifications should appear (e.g. "OTP has been verified successfully."). No blank/empty toasters.
Actual Behavior
A blank green success toast appears with no text content, alongside the actual success message toast. The network tab shows all API calls (verify_otp, link_patient, patient details) returning 200 successfully.
Notes
The blank toast is likely triggered by an API response handler that calls the toast function with an empty or undefined message after one of the linking API calls (verify_otp, link_patient).