Repository navigation
No Intent for APP_MESSAGING #795
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
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
Activity
hiSandog commentedon Jul 9, 2026
A useful next step would be a minimal fixture for No Intent for APP_MESSAGING that includes one failing input and one nearby control case. That would make it clear whether the fix addresses the reported edge case without widening behavior unexpectedly.
github.com/FossifyOrg/Messages/blob/master/CONTRIBUTING.mdis a useful concrete anchor because it is named directly in the report.