[PM-37620] Multiple verification codes showing up for items that don’t have it
- Dominant language
- Swift
- Stars
- 684
- Forks
- 154
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 24
Description
### Steps To Reproduce
Add a verification code to ANY item.
### Expected Result
Go to the verification to find that only the specific item contains that code.
### Actual Result
Go to the verification section to find that MULTIPLE items also have that verification code (same code and timing) without having it registered to that item.
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Build Version
2026.4.1 (3168)
### What server are you connecting to?
US
### Self-host Server Version
_No response_
### Environment Details
© Bitwarden Inc. 2015–2026 📝 Bitwarden 2026.4.1 (3168) 📦 Bundle: com.8bit.bitwarden 📱 Device: iPad16,5 🍏 System: iPadOS 26.4.2 🦀 SDK: 2.0.0-4735-26e2b10 🌩️ Server: 2026.4.2 @ US 🧱 Commit: bitwarden/ios/release/2026.4-rc48@e23637c6e95f8a5fa5a00c0d60e6e7ffc6f61b3b 💻 Build Source: bitwarden/ios/actions/runs/25509673220/attempts/1
### 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.
Contributor guide
Research direction
No source file or test is named. Start by reproducing the issue on the reported iPadOS build: add a verification code to one item and inspect the verification section for other items. Done means only the item with the registered code displays that code and timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100