No Intent for APP_MESSAGING

未关闭
#795 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
57/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
冷清
技术栈
android, kotlin
领域
mobile

调研方向

Open app/src/main/AndroidManifest.xml, identified in the issue, and read the app’s intent-filter declarations. Add the requested APP_MESSAGING category to the appropriate declaration, then verify that setting Fossify Messages as the default launches it instead of another messaging app.

由索引模型根据 Issue 内容生成。

描述

bug needs triage
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

All

Affected Android/Custom ROM version

All

Affected device model

All

How did you install the app?

GitHub releases

Steps to reproduce the bug

install multi laucher on any phone that has any other message app and set this app as default it will always find the first app that has that Intent first then will go for default if none are found

Expected behavior

launch Fossify Messages

Actual behavior

will launch samsung or google messages if installed as they both have the code below

<category android:name="android.intent.category.APP_MESSAGING" />

this should be added to AndroidManifest.xml

Screenshots/Screen recordings

No response

Additional information

No response

主要语言
Kotlin
星标
1.6k
派生
187
平均合并
22 小时 53 分钟
30 天内合并 PR
19

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

FossifyOrg/Messages 的其他 Issue

查看 FossifyOrg/Messages 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。