[Bug]: Agent App Text input state lost on screen rotation
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
Research direction
Start in the Agent Demo screen and locate the text input implementation and its state handling. Reproduce the issue by entering text and rotating the device, then trace what happens during the configuration change. Done means the entered text remains visible after rotating between portrait and landscape.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
Is there a StackOverflow question about this issue?
- I have searched StackOverflow
What happened?
🐛 Bug Report: [Agent app] User Input Cleared on Screen Rotation
Description:
When a user enters text into the text input field and rotates the device from portrait to landscape (or vice-versa), the typed text is completely cleared. The UI state is not persisting across configuration changes.
Steps to Reproduce:
-
Open the Agent application on tab Agent Demo -
Type any random text into the input field. -
Rotate the device to trigger a configuration change. -
Observe that the input field is now empty.
Bug Video below
https://github.com/user-attachments/assets/70e1c632-f693-4330-817a-8e9a4eda2e28
Expected Behavior:
The entered text should survive the rotation and remain visible to the user
Relevant logcat output
Code of Conduct
- I agree to follow this project's Code of Conduct
- Dominant language
- Kotlin
- Stars
- 210
- Forks
- 45
- Avg merge
- 12h 24m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from android/appfunctions
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
android/appfunctions#66 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
android/appfunctions#62 ·
-
Difficulty 4/5 1-2 days Newbie friendliness 55/100
android/appfunctions#64 ·
-
[FR]: Testing agent should handle AppFunctionUriGrant results and pass returned images to the modelOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
android/appfunctions#63 ·
-
Clarify production invocation, Android Auto support, and Android 16 fallback in AppFunctions docsOpen
Difficulty 4/5 3-5 days Newbie friendliness 52/100
android/appfunctions#51 ·
All issues in android/appfunctions
Similar issues
-
pending:code-area pending:issue-category to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
T31n/YagniLauncher#1096 ·
Maintainers usually reply within 1 day
-
win_build: parallel PostBuildEvent race in example_app_atiopencl and example_app_nvopencl copying openclapp_kernels.clPossibly taken @qixuancao claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
OkHttp versions 5.4.0+ no longer include baseline-prof.txtPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 83/100
lysine-dev/okhttp#9828 ·
Maintainers usually reply within 1 day
-
bug Impact: Low Work: Low
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
oppia/oppia-android#6532 · 1 comment ·
Maintainers usually reply within 3 days