Missing attribute support for `<property>` manifest items.
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The payload names no files or classes. Start by finding how the existing Application-level <property> support generates manifest entries, then how the Activity attribute creates <activity> nodes and where the merge duplicates them. Reproduce with the steps in the issue. Done means a C#-side way to declare a property on an activity produces one merged <activity> entry, and a maintainer agrees on the attribute API first.
由索引模型根据 Issue 内容生成。
描述
Android framework version
net11.0-android (Preview)
Affected platform version
Net 10, 11
Description
Activity and Application supports many attributes that generates manifest items, like [Activity], [IntentFilter] etc. Android introduced a new manifest item for activities and application, https://developer.android.com/guide/topics/manifest/property-element a few versions back. Currently, it's only possible to set elements in nodes in manifest and not for nodes. The merging tool duplicates activity entries if you attempt to set it in the manifest file, and no attribute exists that allow the generator to create those entries for
A use case for this is support multi instance mode in the system ui, as explained here https://developer.android.com/develop/adaptive-apps/guides/support-desktop-windowing#multitasking_and_multi-instance https://developer.android.com/develop/ui/views/layout/support-multi-window-mode#multi-instance . Setting it in application scope will affect all activities, including those the user will not want to be created multiple times. Setting it in activity scope is currently not supported, thus this issue is created.
Steps to Reproduce
- Create a new Android application.
- Try adding an activity element in the manifest with the same name as the c# activity.
- Add a property element, like https://developer.android.com/develop/ui/views/layout/support-multi-window-mode#multi-instance .
- When build is complete, the generated manifest has 2 entries with the same activity name.
Did you find any workaround?
No response
Relevant log output
- 主要语言
- C#
- 星标
- 2.1k
- 派生
- 579
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 220
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
dotnet/android 的其他 Issue
-
Area: App+Library Build
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Area: Mono.Android
难度 2/5 1-3 小时 新手友好度 65/100
dotnet/android#9192 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
automated needs-triage skill-runner
难度 1/5 1 小时以内 新手友好度 15/100
维护者通常 1 天内回复
-
Area: App Runtime needs-triage
难度 5/5 一周以上 新手友好度 38/100
维护者通常 1 天内回复
-
Area: App Runtime bug
难度 2/5 1-3 小时 新手友好度 58/100
dotnet/android#13253 · 4 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
good first issue
难度 1/5 1 小时以内 新手友好度 88/100
madeyoga/AuthEndpoints#365 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 76/100
majorsilence/Reporting#493 ·
维护者通常 1 天内回复
-
area: backend enhancement payments
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 4 天内回复