Enatega App Bug: Phone Number Field Accepts Alphabets

by SLV Team 54 views
Enatega Customer Application Bug: Phone Number Field Validation Issue

Hey guys, let's dive into a frustrating bug I found in the Enatega Customer Application. This one's about the phone number field, and how it's letting us enter alphabets when we're trying to log in and verify our phone numbers. Talk about a headache, right?

The Bug: Alphabet Soup in the Phone Number Field

So, the main issue here is pretty straightforward. When you're a new user trying to create an account, or even if you're just logging in and need to verify your phone number, the app should be smart enough to only let you enter digits. That's the whole point, right? Phone numbers are made up of numbers, not letters. However, the Enatega Customer Application is currently allowing users to enter alphabets in the phone number field. This leads to all sorts of problems – failed verification attempts, a messy database, and a generally poor user experience. It's like trying to order a pizza and being asked to spell out the toppings with emojis instead of typing them out! It's clearly not what the developers intended.

This bug makes the user experience really annoying. Imagine trying to log in quickly, only to be stopped by an error message because you accidentally typed a letter instead of a number. It's time-consuming and frustrating. And for the app, it means inaccurate data, which can mess up everything from delivery notifications to marketing campaigns. We definitely want this fixed.

To make it clear, this is a serious usability issue and it should be addressed as quickly as possible. Users will give up and leave, which impacts the app's overall user base.

The Problem in Detail

The phone number field's lack of proper input validation is the core problem here. It's a fundamental requirement for any application that handles phone numbers. The application should check the input format to confirm it's valid before accepting it. It should block any characters that are not digits. This is a common practice, and there are many tools and libraries available to make this process easier. The application should include features like an automatic format checker, where it formats the number when the user types it, or a notification pop-up or a red marking when the format is wrong. This simple step can prevent all sorts of problems. The current lack of this validation leads to a whole cascade of potential issues. Imagine how the app's backend systems are impacted by incorrect phone number formats? The verification process is more complex, marketing and notifications are more complex.

Steps to Reproduce the Bug

It's pretty easy to see this issue for yourself. Here's how:

  1. Open the Enatega Customer Application. Fire up the app on your phone. This is the starting point for seeing the bug.
  2. Choose 'Continue with Email.' Select the option to log in using your email address.
  3. Enter your email and, on the next screen, enter your phone number. After you provide your email, the app will likely prompt you for your phone number for verification.
  4. Try entering alphabets. Now, here's where the fun (or frustration) begins. Tap on the phone number field and start typing in any country phone number. Try to type in some letters instead of numbers. You should be able to do this with no errors.

That's it! You've successfully reproduced the bug. This is what you see when you start using the app. From here, you'll know that the phone number field doesn't have the expected validation.

Additional points on how to reproduce the bug

The app must allow the user to continue using the input even after entering alphabets, without any warnings and any error messages, indicating that this is an error. The user should be able to type any characters on the phone number field and continue logging in.

Expected Behavior: Numbers Only!

What we should see is completely different. The phone number field should be locked down so that only digits can be entered. The app should enforce this at the point of input. This means that: When you tap on the phone number field, the keyboard presented to you should only show numbers and special characters like + and -. When you tap a letter on the keyboard, nothing should happen. No letters, no spaces, no nonsense. The field should only accept the right stuff – numbers. Anything else would be wrong.

If the user is entering a phone number that is not properly formatted, the app should be able to detect this, providing a clear error message. This is all about ensuring data integrity and providing a smooth user experience. Any good app would do this. It is a critical part of preventing issues and ensuring a smooth user experience.

The Impact of the Bug

This might seem like a small detail, but it has some pretty significant implications:

  • Failed Verification: Users will not be able to complete their phone number verification. This will be the first impression of the app and a bad first impression would be a big hit on the app.
  • User Frustration: Nobody likes to see errors when they are just trying to quickly do something. It's an annoyance that can make people give up on using the app, which is something we want to prevent.
  • Data Integrity: The app's database could end up filled with invalid phone numbers. This can lead to all sorts of issues.
  • Poor User Experience: Ultimately, it makes the app look unprofessional and poorly designed.

In the worst-case scenario, this bug could even affect the app's security. It's an issue that should be fixed quickly, as it affects the overall reputation of the app.

Screenshots and Screen Recordings

I have provided a screen recording demonstrating the issue, as well as several screenshots. You can watch the Screen_Recording_20250122_123304.mp4 file to see the bug in action. I was able to enter letters into the phone number field without any problems.

Device and App Information

Here's the info about the device I used:

  • Device: Infinix Hot 50
  • OS: Android
  • Browser: Application
  • Version: 14

This information is important to understand the context of the bug. It may be helpful for developers in identifying the root cause of the bug.

Conclusion

This is a critical issue. The Enatega Customer Application needs to be fixed to ensure the phone number field only accepts digits. This is an important part of any app, and it will prevent all sorts of problems. It will also improve the overall user experience. I hope the team will fix this quickly to prevent further issues and frustration for users. Good luck!