Enatega App: Phone Number Field Accepts Letters - Bug Report

by Dimemap Team 61 views

Hey everyone, let's dive into a frustrating bug I found in the Enatega Customer Application. It's a real head-scratcher, and I wanted to bring it to your attention. Basically, the phone number field in the app is letting users enter alphabets when they're trying to log in or verify their phone number. Talk about a glitch! This creates a problem when it comes to the verification process. I will show you how to reproduce this and what the expected behavior should be.

The Bug: Phone Number Field Accepts Alphabets

So, the core issue here is simple but significant. When a new user attempts to log in to the Enatega Customer Application and reaches the phone number input field, the app incorrectly allows the entry of alphabetical characters. Instead of restricting the field to accept only numerical digits, as you'd expect for a phone number, it welcomes letters with open arms. This is a big deal, as it completely breaks the intended functionality of the phone number field and throws a wrench into the verification process. Phone number verification is one of the most basic security steps, and if the app lets users enter invalid data, it can cause problems for new users. This means the app can not verify the user's phone number, leading to an unusable application. I tested this on my phone and the results were the same. The phone number field must be designed to only accept digits, but it is not behaving as intended. When the user enters their phone number and submits the request, the application should throw an error. But it does not. The lack of validation on a phone number input field makes it a bad practice. The bug is reproducible and poses a risk to the user and the integrity of the application. Imagine you're a new user eager to sign up or log in. You enter your phone number, expecting everything to go smoothly. But then, you realize the field isn't behaving as it should. Instead of a straightforward numeric input, you can type in letters, symbols, or whatever you please. This is not user-friendly and can be frustrating for the user.

This bug not only affects the user experience but can also compromise the app's overall functionality. Phone number verification is often used for security purposes, such as account recovery and two-factor authentication. If the app allows users to enter invalid phone numbers, it undermines these security measures. The app cannot accurately identify users and verify their identities if the phone numbers are invalid. The application needs to be secure and validate any data that the user inputs. This bug directly impacts the reliability of the application's core features. It's a glitch that needs to be fixed to ensure a secure and seamless user experience. It's essential that the developers address this issue promptly to maintain the app's integrity and provide a positive user experience. This also has the potential to cause issues with other features that rely on the phone number field. For example, SMS notifications, order confirmations, or any other services tied to the phone number could be affected. This could cause users to not receive important notifications. This can directly affect business operations.

Steps to Reproduce the Error

Here's how you can replicate the bug yourself, step by step, so you can see it in action:

  1. Open the Enatega Customer Application: Start by launching the app on your device. Make sure you have the latest version installed to ensure you're experiencing the most current state of the application.
  2. Choose 'Continue with email': On the initial screen or login page, find the option that says 'Continue with email' or a similar prompt that allows you to sign up or log in using your email address. It's important to select this option, as this directs you to the phone number input screen.
  3. Enter your phone number: Once you've chosen to continue with email, the app should guide you to a screen where it prompts you to enter your phone number. This is where the magic (or the bug, in this case) happens.
  4. Enter Alphabets in the Phone Number field: The crucial step is to deliberately enter any alphabetical characters into the phone number field. You'll notice that the field doesn't restrict you; you can type letters without any issues. This is where the bug manifests.
  5. Observe the lack of validation: As you type in letters, observe that the application does not prevent you from doing so. There are no error messages or restrictions; the field accepts the input.
  6. Test with Different Countries: It is important to test this on any country phone number. Make sure the results are the same. Check to see if any country number validates your input. It's important to test this thoroughly to make sure this is a global bug.

By following these steps, you can easily reproduce the issue and verify that the phone number field indeed allows alphabetical characters. This will help developers understand the problem and fix it quickly.

Expected Behavior

The expected behavior of the phone number field is straightforward and vital for user experience and data integrity. Here's what should happen:

  1. Numeric Input Only: The phone number field should be designed to accept only numerical digits. The field should be configured to prevent the entry of any non-numeric characters, including letters, symbols, and spaces.
  2. Real-Time Validation: As a user types in the phone number, the app should perform real-time validation to ensure that the input is correct. If a user tries to enter a non-numeric character, the application should not allow it. An immediate error should appear.
  3. Clear Error Messages: If a user somehow manages to enter invalid input, the app should display a clear and helpful error message. This message should tell the user that the phone number field accepts only numbers and provide instructions on what to do next.
  4. Country Code Selection: It is crucial for the application to provide a country code selection. This will assist the user with entering their phone number. It will also validate the correct format of phone numbers and reduce user errors.
  5. Standard Formatting: The phone number field should automatically format the phone number according to standard conventions for the user's country code. This helps users enter valid phone numbers.
  6. Proper Error Handling: When a user submits the form with an invalid phone number, the application should clearly indicate the error and prevent the form submission. This should be consistent with the application's overall design.

By ensuring this behavior, the Enatega Customer Application can provide a user-friendly and secure experience, preventing data entry errors and enhancing the app's reliability. This bug can have a significant impact on security, user experience, and overall functionality.

Screenshots and Additional Information

Unfortunately, I was not able to include screenshots or a video, but the steps above should be easy to follow for any user. I've included all the important information so you should be able to reproduce the error. Here is the technical information, so developers can debug quickly:

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

I hope the developers take a look at this bug. I think with these details, they should be able to replicate the error. This is a very important bug to fix for the application.