API error message displayed to user during phone number verification

Describe the bug
When entering an OTP for phone number verification from the Profile section, a backend error message is shown to the user:
Unknown argument "otp" on field "Mutation.sendOtpToPhoneNumber".
This indicates that the API request payload does not match the backend schema, and the error is not being handled gracefully.

To Reproduce
Steps to reproduce the behavior:

Go to Profile.
Add a phone number and request OTP verification.
Enter the OTP.
Observe the error message displayed in grey over the OTP input area.
Expected behavior

The API request should accept the correct parameters and successfully verify the OTP.
If an error occurs, display a user-friendly message (e.g., "Invalid OTP, please try again.") instead of backend error text.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.

Labels: Enatega Multivendor Customer App, Bug

Start in the Profile phone-number verification flow and search for the sendOtpToPhoneNumber mutation used after OTP entry. Compare its request payload with the backend schema, then inspect how the returned error is rendered over the OTP input. Done means valid OTP verification succeeds and failures show a user-friendly message rather than the backend error text.

Written by the indexing model from the issue text.