FIX: Inconsistency in User Verification Status between Email and Phone Number & Password Field Not Reset On Email Update

[Joyal-George-KJ]

What does this PR do?

• There was a verification status mismatch in the alert/popup when user auth verifying phone number in Appwrite console. The issue has been reported to appwrite/console Repo 🐛 Bug Report: Inconsistency in User Verification Status between Email and Phone Number #1392
• Also addressing this Issue too Password Field Not Reset On Email Update Issue 🐛 Bug Report: Password Field Not Reset On Email Update #976

Changes:

• Issue Inconsistency in User Verification Status between Email and Phone Number 🐛 Bug Report: Inconsistency in User Verification Status between Email and Phone Number #1392:

  • Alert Status mismatch corrected. Added ! to user verification check condition $user.phoneVerification ? 'unverified' : 'verified' changed to !$user.phoneVerification ? 'unverified' : 'verified'.
  • Formatting the name if we are verifying email and has name for user.
  • Formatting the name and email if we are verifying phone number and has name and email for user.
  • Removed The Account from both phone and email verification because the condition is not valid. Condition says that if account has no username, email and phone user use The account instead of using name, email or phone. Which means its an anonymous account that doesn't need verification.
  • Rule followed for the Formatting:
    • XYZ's email has been verified.
    • XYZ's email has been unverified.
    • XYZ's phone has been verified.
    • XYZ's phone has been unverified.

• Issue Password Field Not Reset On Email Update 🐛 Bug Report: Password Field Not Reset On Email Update #976:

  • Just set the emailPassword to null after email updated successfully.

Test Plan

• Checked if the formatting working properly.
• Email Verification Checks
  • Tested name with and without ending with s.
• Phone Verification Checks
  • Tested email and name ending with s and without s.
  • Status alert checked and made sure it was showing right verification status.,

Related PRs and Issues

Addressing Issue #976 : There was this PR #1136 but it had conflicts and wasn't resolved till now (1 month has been passed)

• There was a PR but it didn't follow the Rules and didn't merge, Hence This PR!

Have you read the Contributing Guidelines on issues?

• I have read and followed the Guidelines showing above.

[Joyal-George-KJ]

@stnguyen90 @ItzNotABug PR review request!

[Copilot]

Pull Request Overview

This PR corrects user verification alert messages for email and phone statuses and ensures the password field is cleared after updating the email.

• Fixes inverted logic and message formatting for email and phone verification alerts
• Removes “The account” fallback in notifications and applies consistent phrasing
• Resets emailPassword to null after a successful email update

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
src/routes/(console)/project-[region]-[project]/auth/user-[user]/updateStatus.svelte	Updated notification templates for email and phone verification
src/routes/(console)/account/updateEmail.svelte	Set emailPassword to null after successfully updating email

[Copilot]

Using $user.name && inside a template literal can yield undefined if name is falsy. Consider using a ternary: ${$user.name ? for ${$user.name} : ''} to avoid inserting “undefined.”

Suggested change

	message: `The email${$user.name && ` for ${$user.name}`} ${
	message: `The email${$user.name ? ` for ${$user.name}` : ''} ${

[DH-555]

It's an empty string by default, so not needed

[Copilot]

The dynamic property guard here may insert undefined if both name and email are missing. Use a nested ternary to explicitly handle each case, e.g., ${$user.name ? for ${$user.name}: $user.email ? for ${$user.email} : ''}.

Suggested change

	message: `The phone ${$user[$user.name ? 'name' : 'email'] && `for ${$user[$user.name ? 'name' : 'email']}`}${
	message: `The phone${$user.name ? ` for ${$user.name}` : $user.email ? ` for ${$user.email}` : ''}${

[Copilot]

[nitpick] The leading space on the 'has been verified' branch combined with the preceding template space can result in double spaces. Move spacing outside the conditional or remove the extra leading space for consistency.

Suggested change

	!$user.emailVerification ? 'is no longer verified' : ' has been verified'
	!$user.emailVerification ? 'is no longer verified' : 'has been verified'

[DH-555]

Ooops, small leading space there. I think this is not intentional, right? @Joyal-George-KJ

[Copilot]

[nitpick] Similarly here, both branches include a leading space—consider unifying whitespace handling outside the conditional to prevent inconsistent spacing in the final message.

Suggested change

	message: `The phone ${$user[$user.name ? 'name' : 'email'] && `for ${$user[$user.name ? 'name' : 'email']}`}${
	!$user.phoneVerification ? ' is no longer verified' : ' has been verified'
	message: `The phone ${$user[$user.name ? 'name' : 'email'] && `for ${$user[$user.name ? 'name' : 'email']}`} ${
	!$user.phoneVerification ? 'is no longer verified' : 'has been verified'

[ItzNotABug]

this can be simplified for readability.

[ItzNotABug]

same here.

[coolify-appwrite-org]

The preview deployment is ready. 🟢

Open Preview | Open Build Logs

Last updated at: 2025-07-14 17:17:18 CET

[coolify-appwrite-org]

The preview deployment is ready. 🟢

Open Preview | Open Build Logs

Last updated at: 2025-07-14 17:17:17 CET

[Joyal-George-KJ]

@ItzNotABug and @DH-555: The changes has been made.

• Created a condition check for the presence of user name and email.
• Removed Unwanted space in the notification.

Requesting review.