Lazyweb, I asked before but lost the answer: How do you get rid of dynamic "share to" targets (messaging apps leaking your recent contacts on share-to screen) on Android?
Conversation
Replying to
It's a choice by the messaging apps to list it that way and they would need to provide a toggle. It tends to be the same order they display the chats within the app. It's often who was most recently contacted.
The app triggering the share dialog doesn't see the results of it.
1
1
Replying to
Right, but I recall there was some file you can edit to block these. I just don't remember where it is.
1
1
Replying to
The intent firewall has support for declarative rules.
It's potentially the infrastructure what we'll be using for our scoped app feature in GrapheneOS for preventing an app from communicating with other non-OS components in the same profile. Not necessarily though.
2
2
Replying to
Intent firewall sounds familiar and might be what I was remembering. I think it was some ugly xml file.
1
Replying to
It's XML mimicking the format of how the IPC APIs are defined in an app manifest with selectors to match them. It's a very old feature from the Android 4.x era. In theory, it could have user-facing configuration, but usually only sensible approach is full isolation from non-OS.
1
1
So, for example, you could still open a file from a cloud storage app in another app without those apps directly communicating by using the system file manager to open the file from there. You couldn't share directly to the app from the cloud storage app without it though.
1
So our approach will probably be having a toggle for whether an app can talk to non-base-OS apps in the same profile and once you toggle it off, it could have a an opt-in toggle for enabling communicating with specific non-base-OS apps. Anything more than that is unlikely.