Login fails when using email address with uppercase letters #1932

Closed
opened 2025-11-26 23:02:05 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @CerebralDatabank on GitHub (Jul 6, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Log out if logged in.
  2. Try to log in with an email address with uppercase letters
    Example: John.Smith@example.com + (correct password)
    → Fails with "incorrect username or password"
  3. Try to log in with an email address with all lowercase letters
    Example: john.smith@example.com + (correct password)
    → Succeeds

Expected Result

Logging in should work regardless of the case of the characters in the email address.

That would also match the behavior of the existing Xamarin Android app, web app, and browser extensions.

Actual Result

Logging in with an email address with uppercase characters fails, while an all-lowercase email address succeeds.

Screenshots or Videos

Screen when login fails:

bitwarden-beta-email-issue

Additional Context

This problem was found on a fresh install of Bitwarden Beta on a Pixel (Android) device.

Build Version

2024.6.1

Environment Details

  • Device: Pixel 8 Pro
  • OS: Android 14

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @CerebralDatabank on GitHub (Jul 6, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Log out if logged in. 2. Try to log in with an email address with uppercase letters Example: `John.Smith@example.com` + `(correct password)` → Fails with "incorrect username or password" 3. Try to log in with an email address with all lowercase letters Example: `john.smith@example.com` + `(correct password)` → Succeeds ### Expected Result Logging in should work regardless of the case of the characters in the email address. That would also match the behavior of the existing Xamarin Android app, web app, and browser extensions. ### Actual Result Logging in with an email address with uppercase characters fails, while an all-lowercase email address succeeds. ### Screenshots or Videos Screen when login fails: <img src="https://github.com/bitwarden/android/assets/24465111/cd1fc11c-02fa-4d70-a831-5c318de4463c" alt="bitwarden-beta-email-issue" width="400"> ### Additional Context This problem was found on a fresh install of Bitwarden Beta on a Pixel (Android) device. ### Build Version 2024.6.1 ### Environment Details - Device: Pixel 8 Pro - OS: Android 14 ### Issue Tracking Info - [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug label 2025-11-26 23:02:05 -06:00
Author
Owner

@JuliusBairaktaris commented on GitHub (Jul 6, 2024):

According to RFC 5321, the local part of an email address should be treated as case-sensitive. Therefore, the behavior you describe is correct and wanted.

@JuliusBairaktaris commented on GitHub (Jul 6, 2024): According to RFC 5321, the local part of an email address should be treated as case-sensitive. Therefore, the behavior you describe is correct and wanted.
Author
Owner

@Hinton commented on GitHub (Jul 8, 2024):

Hi @CerebralDatabank,

Thanks for reporting this. This seems indeed to not be the desired behaviour as it's inconsistent with the other applications.

@Hinton commented on GitHub (Jul 8, 2024): Hi @CerebralDatabank, Thanks for reporting this. This seems indeed to not be the desired behaviour as it's inconsistent with the other applications.
Author
Owner

@Hinton commented on GitHub (Jul 18, 2024):

This should have been released as part of 2024.7.0 or 2024.7.1. Closing but let me know if this is still an issue.

@Hinton commented on GitHub (Jul 18, 2024): This should have been released as part of 2024.7.0 or 2024.7.1. Closing but let me know if this is still an issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1932