Capital letters bug on beginning of typing in (new) app
Maintainers usually reply within 1 day
@LeanBitLab is already working on this.
Since Oct 29, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
Research direction
The payload names no source files, tests or entry points; the only artifact is a diagnostic zip attached by the reporter, which lives outside the repository. Start by checking whether the issue reproduces on a current build, then inspect the zip's logs for when the keyboard's shift state is set and not cleared. Done means the first letter is the only capital after a fresh app open, with a regression test or a reproduction that a reviewer can confirm.
Written by the indexing model from the issue text.
Description
Describe the bug
Sometimes (not rarely, but not often), when i start typing in some app, letters stay capital/uppercase after 1st letter
To Reproduce
Not reproducable, it's noticed randomly, but i think it mostly happenes in (new) apps we open first time after some time pass from last usage of that app. Closing app from recent apps and opening it doesn't help reproducing this bug
Expected behavior
Letters should become small after 1st letter was typed, and eventually it should not conflict with earlier fixes related to fast typing (if it even conflicts or has relation with it at all, maybe it doesn't)
Screenshots
https://github.com/user-attachments/assets/29bfa17e-d643-4a40-9c25-7b11ade11062
App version & Flavor
beta-430-1 , standard release
Device Info
- Model: Samsung Galaxy S23
- OS version: Android 17
Additional
I made patch zip file which has log for diagnostic, but didn't have time to build apk with it, and won't be able to do that or test it in next 12 hours, so in case you want to use it to find cause of this issue, sharing zip here:
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 59
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 56
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 LeanBitLab/LeanType
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
LeanBitLab/LeanType#745 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
LeanBitLab/LeanType#738 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 70/100
LeanBitLab/LeanType#724 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 56/100
LeanBitLab/LeanType#721 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
LeanBitLab/LeanType#699 ·
Maintainers usually reply within 1 day
All issues in LeanBitLab/LeanType
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
enorm-labs/event-junkie#4221 ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
leonlatsch/Photok#816 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
owenlejeune/ArrMatey#417 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
orgzly-revived/orgzly-android-revived#1120 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Tiqr/eduid-app-android#277 ·