Describe the bug
AFWall+ does not reliably show apps that are installed ONLY in a work profile or ONLY in private space. If an app is installed only in one of those spaces, it will not appear in the app list of AFWall and cannot be assigned firewall rules. In some cases such as when installed in all 3 profiles, both entries(Work & Private Spaces) are shown with the same (M) marker, which is confusing and makes it hard to tell them apart.
This is not a new problem. It has been reported numerous times before such as #1249, #869, #1410, #1325, #1482 and appears to be a long-standing AFWall+ bug, going back to Android 10 or earlier.
Smartphone (please complete the following information):
- Device: OP11
- Android OS: LOS 23 (Android 16)
- AFWall v4.0.3 (Latest)
Additional context
Expected behavior:
AFWall+ should detect apps from both work profile and private space, and it should label them clearly so they are easy to distinguish.
Actual behavior:
Apps installed only in work profile or only in private space will not appear at all. When they do appear, the current markers are unclear because both entries can show the same (M) symbol.
Steps to reproduce:
- Set up a work profile or private space.
- Install an app only in that profile.
- Open AFWall+ and refresh the app list.
- The app will not appear.
- If the same app is installed in the main profile too, it will appear.
Notes:
There are no logs to attach for this issue, because the problem is about app detection and labeling, not a crash or runtime error. The issue is visible directly in the app list.
The bad Workaround
You have to KEEP THE APP INSTALLED IN MAIN PROFILE TO SEE THE APP IN THE AFWall LIST FROM other PROFILES, this WASTES SPACE on the phone, EVEN if you "disable" the app in main profile.
So in summary there are 2 problems:
- the app must be duplicated in order to appear in the AFWall app list, and
- the label for both Work Profile and Private Space is the same, (M), which makes them impossible to tell apart. - What about making (W) for Work Profile and (P) for Private Spaces ?
@ukanth appreciate it if you can give these 2 problems some attention please, especially problem 1.
Describe the bug
AFWall+ does not reliably show apps that are installed ONLY in a work profile or ONLY in private space. If an app is installed only in one of those spaces, it will not appear in the app list of AFWall and cannot be assigned firewall rules. In some cases such as when installed in all 3 profiles, both entries(Work & Private Spaces) are shown with the same (M) marker, which is confusing and makes it hard to tell them apart.
This is not a new problem. It has been reported numerous times before such as #1249, #869, #1410, #1325, #1482 and appears to be a long-standing AFWall+ bug, going back to Android 10 or earlier.
Smartphone (please complete the following information):
Additional context
Expected behavior:
AFWall+ should detect apps from both work profile and private space, and it should label them clearly so they are easy to distinguish.
Actual behavior:
Apps installed only in work profile or only in private space will not appear at all. When they do appear, the current markers are unclear because both entries can show the same (M) symbol.
Steps to reproduce:
Notes:
There are no logs to attach for this issue, because the problem is about app detection and labeling, not a crash or runtime error. The issue is visible directly in the app list.
The bad Workaround
You have to KEEP THE APP INSTALLED IN MAIN PROFILE TO SEE THE APP IN THE AFWall LIST FROM other PROFILES, this WASTES SPACE on the phone, EVEN if you "disable" the app in main profile.
So in summary there are 2 problems:
@ukanth appreciate it if you can give these 2 problems some attention please, especially problem 1.