Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Failed to change email address in Android app #6271

Open
TripleCamellya opened this issue Mar 27, 2025 · 1 comment
Open

bug: Failed to change email address in Android app #6271

TripleCamellya opened this issue Mar 27, 2025 · 1 comment
Labels

Comments

@TripleCamellya
Copy link

TripleCamellya commented Mar 27, 2025

Describe the Bug

Failed to change email address on Android app through profile page.

The page said it saved changes successfully. But after exiting, it rollbacked to original email address.

Steps to Reproduce

  1. Using Android app. Go to profile page.
  2. Change a new email address.
  3. Click save changes.
  4. App asks you to enter your password, then enter the password for the account.
  5. App says profile saved successfully.
  6. Exit the profile page and enter it again. The email will still be original one.

Expected Behavior

When entering again, the email address should be a new one.

Actual Behavior

The email address reverted to original one.

Image

It is also different from website. For website, it uses email authentication code to save changes, instead of password. I can change my email address permanently in website.

Image

Rocket.Chat Server Version

7.5.0

Rocket.Chat App Version

4.58.0.74631

Device Name

Honor Magic 7

OS Version

Android13

Additional Context

No response

JASIM0021 added a commit to JASIM0021/Rocket.Chat.ReactNative that referenced this issue Mar 28, 2025
JASIM0021 added a commit to JASIM0021/Rocket.Chat.ReactNative that referenced this issue Mar 28, 2025
JASIM0021 added a commit to JASIM0021/Rocket.Chat.ReactNative that referenced this issue Mar 28, 2025
@JASIM0021
Copy link
Contributor

I have made some changes; please review this PR #6276. This will fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants