The system presents a critical bug during phone number updates and validation where the default international prefix (+1) forcefully persists and interferes when attempting to input a different prefix (+53), preventing the user's entered number from being saved correctlyspan_0span_0.
Issue Description
When attempting to update the phone number in the designated section, the input rigidly locks onto the default prefix (+1)span_1span_1. When a user tries to enter a phone number with a different country code (such as Cuba's +53), a formatting conflict occurs. The system fails to properly process or store the entered area codespan_2span_2, consequently breaking the SMS verification code dispatch and validation flow.
Preconditions
The user is on the phone number update screen (Verifica tu cuenta / SMS section)span_3span_3.
The input field for the new phone number contains a rigid default prefix (+1)span_4span_4.
Steps to Reproduce
Navigate to the phone number update sectionspan_5span_5.
Attempt to enter a new phone number starting with a different international prefix (e.g., +5355239758)span_6span_6.
Observe how the default prefix (+1) persists or conflicts with the entered formatspan_7span_7.
Click on Actualizar y enviar código (Update and send code)span_8span_8.
Verify that the system fails to correctly save the code or process the phone number properlyspan_9span_9.
Expected Result
The phone number input should allow clean replacement or dynamic selection of the international prefix, or alternatively feature a scrollable dropdown menu containing all existing international telephone dialing codes worldwide to prevent formatting conflicts and ensure proper number persistence.
Actual Result
The +1 prefix forcefully persists despite trying to input a number with +53, the system fails to save the area code correctly, and the phone update flow breaksspan_10span_10.
Evidence
Affected Input: Field "Ingresa el nuevo teléfono (p. ej., +1 555-123-4567)span_11"span_11.
Visual/Functional Conflict: The +1 prefix remains static, blocking the correct registration of international numbers (e.g., code +53)span_12span_12.
Flow Impact: The number is not stored adequately, and the SMS validation process is disruptedspan_13span_13.
Impact
Functional Blocker: International users or those with prefixes other than +1 cannot update their contact information or receive verification codesspan_14span_14.
Data Integrity: The system stores incorrect or incomplete data due to poor telephone input sanitization.
It is recommended to redesign the phone input component by separating the country code selector from the local number field, or by implementing a scrollable dropdown menu that includes all existing international telephone dialing codesspan_17span_17.
Ensure backend logic and the database correctly store the user-selected prefix without overriding it with default values (+1)span_18span_18.
## Summary
The system presents a critical bug during phone number updates and validation where the default international prefix (+1) forcefully persists and interferes when attempting to input a different prefix (+53), preventing the user's entered number from being saved correctly[span_0](start_span)[span_0](end_span).
## Issue Description
When attempting to update the phone number in the designated section, the input rigidly locks onto the default prefix (+1)[span_1](start_span)[span_1](end_span). When a user tries to enter a phone number with a different country code (such as Cuba's +53), a formatting conflict occurs. The system fails to properly process or store the entered area code[span_2](start_span)[span_2](end_span), consequently breaking the SMS verification code dispatch and validation flow.
## Preconditions
- The user is on the phone number update screen (Verifica tu cuenta / SMS section)[span_3](start_span)[span_3](end_span).
- The input field for the new phone number contains a rigid default prefix (+1)[span_4](start_span)[span_4](end_span).
## Steps to Reproduce
1. Navigate to the phone number update section[span_5](start_span)[span_5](end_span).
2. Attempt to enter a new phone number starting with a different international prefix (e.g., +5355239758)[span_6](start_span)[span_6](end_span).
3. Observe how the default prefix (+1) persists or conflicts with the entered format[span_7](start_span)[span_7](end_span).
4. Click on *Actualizar y enviar código* (Update and send code)[span_8](start_span)[span_8](end_span).
5. Verify that the system fails to correctly save the code or process the phone number properly[span_9](start_span)[span_9](end_span).
## Expected Result
The phone number input should allow clean replacement or dynamic selection of the international prefix, or alternatively feature a scrollable dropdown menu containing all existing international telephone dialing codes worldwide to prevent formatting conflicts and ensure proper number persistence.
## Actual Result
The +1 prefix forcefully persists despite trying to input a number with +53, the system fails to save the area code correctly, and the phone update flow breaks[span_10](start_span)[span_10](end_span).
## Evidence
- *Affected Input:* Field "Ingresa el nuevo teléfono (p. ej., +1 555-123-4567)[span_11](start_span)"[span_11](end_span).
- *Visual/Functional Conflict:* The +1 prefix remains static, blocking the correct registration of international numbers (e.g., code +53)[span_12](start_span)[span_12](end_span).
- *Flow Impact:* The number is not stored adequately, and the SMS validation process is disrupted[span_13](start_span)[span_13](end_span).
## Impact
- *Functional Blocker:* International users or those with prefixes other than +1 cannot update their contact information or receive verification codes[span_14](start_span)[span_14](end_span).
- *Data Integrity:* The system stores incorrect or incomplete data due to poor telephone input sanitization.
## Frequency
Always[span_15](start_span)[span_15](end_span)
## Reproducibility
100%[span_16](start_span)[span_16](end_span)
## Notes & Recommendations
- It is recommended to redesign the phone input component by separating the country code selector from the local number field, or by implementing a scrollable dropdown menu that includes all existing international telephone dialing codes[span_17](start_span)[span_17](end_span).
- Ensure backend logic and the database correctly store the user-selected prefix without overriding it with default values (+1)[span_18](start_span)[span_18](end_span).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The system presents a critical bug during phone number updates and validation where the default international prefix (+1) forcefully persists and interferes when attempting to input a different prefix (+53), preventing the user's entered number from being saved correctlyspan_0span_0.
Issue Description
When attempting to update the phone number in the designated section, the input rigidly locks onto the default prefix (+1)span_1span_1. When a user tries to enter a phone number with a different country code (such as Cuba's +53), a formatting conflict occurs. The system fails to properly process or store the entered area codespan_2span_2, consequently breaking the SMS verification code dispatch and validation flow.
Preconditions
Steps to Reproduce
Expected Result
The phone number input should allow clean replacement or dynamic selection of the international prefix, or alternatively feature a scrollable dropdown menu containing all existing international telephone dialing codes worldwide to prevent formatting conflicts and ensure proper number persistence.
Actual Result
The +1 prefix forcefully persists despite trying to input a number with +53, the system fails to save the area code correctly, and the phone update flow breaksspan_10span_10.
Evidence
Impact
Frequency
Alwaysspan_15span_15
Reproducibility
100%span_16span_16
Notes & Recommendations