Chrome WebApps have incorrect icons in the app drawer and home screen
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The payload names no files or tests. Start by searching the Kotlin codebase for where Chrome web app shortcuts get their icons for the app drawer and home screen, and check whether the icon lookup is keyed by something that several web apps share. Reproduce with two or more web apps installed from Chrome, then confirm each one shows its own icon. Done means every web app in the drawer and on the home screen shows its own icon, and the existing icon behaviour for other apps is unchanged.
由索引模型根据 Issue 内容生成。
描述
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.7.0
Affected Android/Custom ROM version
Android 14
Affected device model
Xiaomi POCO X6 Pro 5G
How did you install the app?
Google Play Store
Steps to reproduce the bug
I swipe up and open the file drawer or add icons to the homescreen from it (usually into folders).
Expected behavior
The expected behavior is that all WebApps should have their own separate icons that don't interfere with each other in any way.
Actual behavior
I see that a lot of WebApps choose icons from other existing WebApps instead of their own ones. Recent apps and app info work as expected though.
Screenshots/Screen recordings
Additional information
No response
- 主要语言
- Kotlin
- 星标
- 703
- 派生
- 85
- 平均合并
- 1 天 17 小时
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FossifyOrg/Launcher 的其他 Issue
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 78/100
FossifyOrg/Launcher#453 ·
维护者通常 1 天内回复
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 70/100
FossifyOrg/Launcher#447 ·
维护者通常 1 天内回复
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 72/100
FossifyOrg/Launcher#446 ·
维护者通常 1 天内回复
-
Lock disposition未关闭feature request needs triage
难度 3/5 1-2 天 新手友好度 45/100
FossifyOrg/Launcher#469 · 2 条评论 ·
维护者通常 1 天内回复
-
feature request needs triage
难度 3/5 1-2 天 新手友好度 58/100
FossifyOrg/Launcher#465 ·
维护者通常 1 天内回复
查看 FossifyOrg/Launcher 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
OpenAPITools/openapi-generator#25454 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 74/100
googleads/googleads-mobile-android-mediation#1675 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
navikt/mock-oauth2-server#1149 ·
维护者通常 1 天内回复
-
triaged
难度 1/5 1 小时以内 新手友好度 65/100
维护者通常 1 天内回复