Invisible app drawer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
The payload names no files or tests. Start by reproducing the app drawer opening under the swipe-up gesture, and check whether its opacity or alpha is being set to zero when the drawer appears. Read the linked issue #69 first, since the reporter suspects it is the same bug. Done would mean a reliable reproduction plus a fix that keeps the drawer visible, but the reporter could not reproduce it reliably, so the scope is unclear.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.0.1
Affected Android/Custom ROM version
Android 13 and above (I think)
Affected device model
Motorola (stock), Xiaomi with custom Android 15
How did you install the app?
GitHub releases
Steps to reproduce the bug
Open app drawer by swiping up, I can't reproduce it reliably.
It's very rare, it happened only a couple times since the initial release.
Expected behavior
No invisible drawer
Actual behavior
Invisible drawer. Launching apps and long press still works so it has something to do with opacity.
Screenshots/Screen recordings
No response
Additional information
This could be related to or the same issue as https://github.com/FossifyOrg/Launcher/issues/69
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No 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 FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 58/100
FossifyOrg/Launcher#465 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Launcher
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days
-
coding good first issue size:xs skill:kotlin-core sub-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
SKaiNET-developers/SKaiNET#1323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dzid26/TeslaBatteryBLE#183 ·
Maintainers usually reply within 1 day