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

System UI animination stuck when Bitwarden Autofill Accessibility service is on #2109

New Issue
Closed
opened 2025-11-26 23:08:22 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 23:08:22 -06:00
Owner
Copy Link

Originally created by @gitiray on GitHub (Dec 20, 2024).

Steps To Reproduce

  1. Install the latest Native version of Bitwarden
  2. Enable autofill accessability service
  3. Swip up the navigation bar to the multi-task center, you can notice the transition animination has a short stuck everytime if you repeate the swip-up action.
  4. Turn off autofill accessability service
  5. Swip up the navigation bar AGAIN to the multi-task center, no longer animination stuck. It's quite smooth.

Expected Result

System UI smoothability not affected.

Actual Result

The transition animination to multi-task center has a short stuck everytime when you repeate the swip-up action.

Screenshots or Videos

No response

Additional Context

The problem is quite severe in the earily version of Native Bitwarden, and was great improved later since a version (I don't really remember the version code).
Now it still has a little bit impact, so I hope it can be fixed completedly.

Build Version

2024.11.7 (19528)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

  • 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.
Originally created by @gitiray on GitHub (Dec 20, 2024). ### Steps To Reproduce 1. Install the latest Native version of Bitwarden 2. Enable autofill accessability service 3. Swip up the navigation bar to the multi-task center, you can notice the transition animination has a short stuck everytime if you repeate the swip-up action. 4. Turn off autofill accessability service 5. Swip up the navigation bar AGAIN to the multi-task center, no longer animination stuck. It's quite smooth. ### Expected Result System UI smoothability not affected. ### Actual Result The transition animination to multi-task center has a short stuck everytime when you repeate the swip-up action. ### Screenshots or Videos _No response_ ### Additional Context The problem is quite severe in the earily version of Native Bitwarden, and was great improved later since a version (I don't really remember the version code). Now it still has a little bit impact, so I hope it can be fixed completedly. ### Build Version 2024.11.7 (19528) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:08:22 -06:00
GiteaMirror commented 2025-11-26 23:08:22 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 20, 2024):

Thank you for your report! We've added this to our internal board for review.
ID: PM-16254

@bitwarden-bot commented on GitHub (Dec 20, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-16254
GiteaMirror commented 2025-11-26 23:08:22 -06:00
Author
Owner
Copy Link

@daniellbw commented on GitHub (Dec 20, 2024):

Hi there,

This report has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@daniellbw commented on GitHub (Dec 20, 2024): Hi there, This report has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 23:08:23 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 12, 2025):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (August 26, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

@closebot-bw commented on GitHub (Aug 12, 2025): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (August 26, 2025) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2025-11-26 23:08:23 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 23, 2025):

🔔 Final Notice - Issue Will Be Closed Soon

This issue was previously marked as stale and will be automatically closed in 3 days (August 26, 2025) if no further activity occurs.

If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure.

We appreciate your understanding and contribution to keeping our issue tracker organized! 📋

@closebot-bw commented on GitHub (Aug 23, 2025): 🔔 **Final Notice - Issue Will Be Closed Soon** This issue was previously marked as stale and will be automatically closed in **3 days** (August 26, 2025) if no further activity occurs. If you're still experiencing this issue or believe it should remain open, please comment below to prevent automatic closure. We appreciate your understanding and contribution to keeping our issue tracker organized! 📋
GiteaMirror commented 2025-11-26 23:08:23 -06:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Aug 26, 2025):

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

  • Please create a new issue with updated information
  • Include steps to reproduce the problem if it's a bug report
  • Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏

@closebot-bw commented on GitHub (Aug 26, 2025): 🔒 **Issue Closed Due to Inactivity** This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities. **If this issue is still relevant:** - Please create a new issue with updated information - Include steps to reproduce the problem if it's a bug report - Mention if this issue still occurs in the latest version Thank you for your contribution to this project. Your feedback helps us improve! 🙏
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 app:password-manager bug
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#2109
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?