Accidently creating invisible folders in dock
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
The payload names no source files or tests. Start by reproducing the bug on the Kotlin launcher from the repository, dragging an app onto an occupied bottom-right dock cell, then find the drop-handling code that creates folders from dock items. Done means dropping onto an occupied dock slot either opens a visible, usable folder or is refused, and no empty invisible folder is left behind.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.6.0
Affected Android/Custom ROM version
Android 16
Affected device model
Pixel 10 PRO XL
How did you install the app?
Google Play Store
Steps to reproduce the bug
- Have a app on the bottom right most location on your app dock at home screen.
- Drag and drop another app or same app onto the bottom right most location where you should already have a app there.
- Invisible folder is created and takes up that space.
Expected behavior
A folder should not be able to be created in the dock at home screen as this is not a feature yet. One should be able to manipulate the apps in this folder by click on the folder in attempt to manipulate the apps within it. Please feel free to correct me if I am wrong.
Actual behavior
Invisible folder is created and takes up that space. One can add more and more apps into this invisible folder. One can not access the invisible folder without attempt to add more apps to this invisible folder.
Screenshots/Screen recordings
https://drive.proton.me/urls/0VTTC2D6TM#QvG10FnpNM2M
Additional information
Fix:
- Drag and attempt to drop another app to that bugged location where the invisible folder is located on your dock at home screen.
- Quickly move the wanted app during attempt to a non-dock location at home screen.
- Ensure the invisible folder appears and stays open. (If the invisible folder does not stay open in order for one to remove the existing app in it, redo fix steps 1 & 2.)
- Touch and hold app in the invisible folder and remove it.
- Ensure that no more apps are in this invisible folder by attempting fix steps 1 & 2 again or if the invisible folder is still open then remove the remaining apps in it.
- Once all apps are removed from the invisible folder in the dock at home screen, one should now be able to successfully place a app in that location on the dock at home screen without issue.
*Note: One might have to perform the above fix a couple of times in order to successfully place a app in that location on the dock at home screen. Please refer to the uploaded MP4 file for reference.
**Note 2: There could be more than one spot on the dock at home screen that can get this invisible folder.
- Lenguaje dominante
- Kotlin
- Estrellas
- 703
- Forks
- 85
- Merge medio
- 2 d 22 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Launcher
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
FossifyOrg/Launcher#453 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Launcher#447 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
FossifyOrg/Launcher#446 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
FossifyOrg/Launcher#465 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 40/100
FossifyOrg/Launcher#461 ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Launcher
Issues similares
-
Dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ankidroid/Anki-Android#22555 ·
Los mantenedores suelen responder en 1 día
-
Good first issue: add kotlin-spring-boot stack budget preset (Kotlin + Spring Boot 3 + Gradle)Abiertoenhancement good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
core: RAC_LLM_OPTIONS_DEFAULT.min_p disagrees with the IDL's annotated defaultPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug core p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
RunanywhereAI/runanywhere-sdks#1083 ·
Los mantenedores suelen responder en 5 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Java and Kotlin (JVM): parse gradle/wrapper/gradle-wrapper.properties with exact line locationsAbiertoarea: detector eco: java help wanted lane: free-agent roadmap size: S type: parser
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
arminazimi/evergreen#355 ·
Los mantenedores suelen responder en 1 día