TeamAmaze / TeamAmaze/AmazeFileManager

Keyboard appears unexpectedly after clicking 'OK' on 'Encrypt' dialog

Open
#4,306 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Easy (good first issue) Issue-Glitch
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Describe the Bug
The 'Encrypt' dialog closes, and the keyboard unexpectedly appears after clicking 'OK'.

Steps to Reproduce

  1. Click the 3 Vertical Dots icon next to a file.
  2. Select 'Encrypt'.
  3. Enter a password in the first password field (e.g., '123').
  4. Enter the same password in the second password field.
  5. Click the 'OK' button.

Expected Behavior
The 'Encrypt' dialog should close smoothly without the keyboard appearing.

Screen Recording

https://github.com/user-attachments/assets/53f9360d-54d5-44b2-8433-38521edc9134

Smartphone (please complete the following information):

  • Device: [Google Pixel 5]
  • OS: [Android 14]
  • Rooted: [No]
  • Version: [v3.10]

Additional notes
This issue also triggers the 'refresh' function.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Encrypt dialog flow on Android 14 using the listed steps and inspect the code handling the dialog's OK action. Verify that closing the dialog does not reopen the keyboard or trigger the refresh function, then confirm the behavior on the reported Google Pixel 5 configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.