github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[PR #3401] [MERGED] PM-9077: Ensure each PendingIntent for inline autofill uses unique requestCode #16955

New Issue
Closed
opened 2026-04-15 02:33:58 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 02:33:58 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/3401
Author: @david-livefront
Created: 7/3/2024
Status: ✅ Merged
Merged: 7/8/2024
Merged by: @david-livefront

Base: main ← Head: PM-9077-gboard-autofill-bug

📝 Commits (1)

  • 190d54f PM-9077: Ensure each PendingIntent for inline autofill uses unique requestCode

📊 Changes

1 file changed (+8 additions, -10 deletions)

View changed files

📝 app/src/main/java/com/x8bit/bitwarden/data/autofill/util/AutofillIntentUtils.kt (+8 -10)

📄 Description

🎟️ Tracking

PM-9077

📔 Objective

This PR addresses a bug in inline autofill where having multiple options that can be used to fill the same field causes the PendingIntents to not function at all. The request codes for the pending intents are now based on random UUIDs ensuing unique request codes.

⏰ 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

🔄 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/3401 **Author:** [@david-livefront](https://github.com/david-livefront) **Created:** 7/3/2024 **Status:** ✅ Merged **Merged:** 7/8/2024 **Merged by:** [@david-livefront](https://github.com/david-livefront) **Base:** `main` ← **Head:** `PM-9077-gboard-autofill-bug` --- ### 📝 Commits (1) - [`190d54f`](https://github.com/bitwarden/android/commit/190d54f28013d42d7a349325d58d91c79bc0ac48) PM-9077: Ensure each PendingIntent for inline autofill uses unique requestCode ### 📊 Changes **1 file changed** (+8 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/java/com/x8bit/bitwarden/data/autofill/util/AutofillIntentUtils.kt` (+8 -10) </details> ### 📄 Description ## 🎟️ Tracking [PM-9077](https://bitwarden.atlassian.net/browse/PM-9077) ## 📔 Objective This PR addresses a bug in inline autofill where having multiple options that can be used to fill the same field causes the PendingIntents to not function at all. The request codes for the pending intents are now based on random UUIDs ensuing unique request codes. ## ⏰ 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 [PM-9077]: https://bitwarden.atlassian.net/browse/PM-9077?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --- <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 02:33:58 -05: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#16955
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?