github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 22:25:22 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[PR #3596] [PM-6702] Email verification feature #4272

New Issue
Closed
opened 2025-11-26 23:42:15 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:42:15 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/bitwarden/android/pull/3596

State: closed
Merged: No

🎟️ Tracking

PM-6701 Self-host registration
PM-6702 Cloud flow registration
PM-8947 Add support for marketing email consent

📔 Objective

Feature to separate the account creation into 2 separate steps. First step the user enter the email, name and marketing consent. The second step is the password setup. If the app is configured for a BW cloud environment, the user will receive an email to complete the registration process and access the 2 step of the flow.

📸 Screenshots

image image image

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation 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
**Original Pull Request:** https://github.com/bitwarden/android/pull/3596 **State:** closed **Merged:** No --- ## 🎟️ Tracking <!-- Paste the link to the Jira or GitHub issue or otherwise describe / point to where this change is coming from. --> [PM-6701 Self-host registration](https://bitwarden.atlassian.net/browse/PM-6701) [PM-6702 Cloud flow registration](https://bitwarden.atlassian.net/browse/PM-6702) [PM-8947 Add support for marketing email consent ](https://bitwarden.atlassian.net/browse/PM-8947) ## 📔 Objective <!-- Describe what the purpose of this PR is, for example what bug you're fixing or new feature you're adding. --> Feature to separate the account creation into 2 separate steps. First step the user enter the email, name and marketing consent. The second step is the password setup. If the app is configured for a BW cloud environment, the user will receive an email to complete the registration process and access the 2 step of the flow. ## 📸 Screenshots <!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. --> <img width="361" alt="image" src="https://github.com/user-attachments/assets/60b00062-1f44-469b-bf2d-88faa474cbfe"> <img width="362" alt="image" src="https://github.com/user-attachments/assets/3e101bd6-7591-4036-a20e-2d0db2fac5b1"> <img width="360" alt="image" src="https://github.com/user-attachments/assets/fb4612c4-deb9-46b3-9d01-7f84ae998b20"> ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation 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
GiteaMirror added the pull-request label 2025-11-26 23:42:15 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#4272
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?