[PR #6070] [MERGED] [PM-26810] Clear password input after successful OTP verification #19040

Closed
opened 2026-04-15 03:37:25 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/6070
Author: @SaintPatrck
Created: 10/22/2025
Status: Merged
Merged: 10/23/2025
Merged by: @SaintPatrck

Base: mainHead: PM-26810/clear-totp-input


📝 Commits (1)

  • fef7bf0 [PM-26810] Clear password input after successful OTP verification

📊 Changes

2 files changed (+19 additions, -14 deletions)

View changed files

📝 app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/exportitems/verifypassword/VerifyPasswordViewModel.kt (+1 -1)
📝 app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/exportitems/verifypassword/VerifyPasswordViewModelTest.kt (+18 -13)

📄 Description

🎟️ Tracking

PM-26810

📔 Objective

This commit addresses an issue where the verification code input field was not cleared after a successful Two-Factor Authentication (2FA) verification during the item export process.

When handling a VerifyOtpResult.Verified action, the view model state is now updated to reset the input field to an empty string. This ensures the verification code is no longer visible in the input field after the OTP dialog is dismissed and the user proceeds.

📸 Screenshots

Coming soon!

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/6070 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 10/22/2025 **Status:** ✅ Merged **Merged:** 10/23/2025 **Merged by:** [@SaintPatrck](https://github.com/SaintPatrck) **Base:** `main` ← **Head:** `PM-26810/clear-totp-input` --- ### 📝 Commits (1) - [`fef7bf0`](https://github.com/bitwarden/android/commit/fef7bf09dfa72dcb70bf57abf516c2a1914e85a6) [PM-26810] Clear password input after successful OTP verification ### 📊 Changes **2 files changed** (+19 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/kotlin/com/x8bit/bitwarden/ui/vault/feature/exportitems/verifypassword/VerifyPasswordViewModel.kt` (+1 -1) 📝 `app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/exportitems/verifypassword/VerifyPasswordViewModelTest.kt` (+18 -13) </details> ### 📄 Description ## 🎟️ Tracking PM-26810 ## 📔 Objective This commit addresses an issue where the verification code input field was not cleared after a successful Two-Factor Authentication (2FA) verification during the item export process. When handling a `VerifyOtpResult.Verified` action, the view model state is now updated to reset the `input` field to an empty string. This ensures the verification code is no longer visible in the input field after the OTP dialog is dismissed and the user proceeds. ## 📸 Screenshots Coming soon! ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 03:37:25 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#19040