Hi, thank you for the amazing app!
I recently updated to Android 17, and I noticed that cross-profile loopback communication (like sharing a proxy via 127.0.0.1 to a work profile) is now strictly blocked by default due to OS changes.
I was searching for a workaround and found that if an app declares <uses-permission android:name="android.permission.INTERACT_ACROSS_USERS" /> in its AndroidManifest.xml, users can manually grant this permission via ADB to bypass the restriction.
(Reference: VentralDigital/InterProfileSharing#34 )
Would it be possible to consider adding this permission line to the manifest in a future update?
It wouldn't affect normal users since it remains ungranted unless an ADB command is used, but it would be a huge lifesaver for Android 17 users who need cross-profile routing.
Thank you for your time and all the hard work on this project!
Hi, thank you for the amazing app!
I recently updated to Android 17, and I noticed that cross-profile loopback communication (like sharing a proxy via
127.0.0.1to a work profile) is now strictly blocked by default due to OS changes.I was searching for a workaround and found that if an app declares
<uses-permission android:name="android.permission.INTERACT_ACROSS_USERS" />in itsAndroidManifest.xml, users can manually grant this permission via ADB to bypass the restriction.(Reference: VentralDigital/InterProfileSharing#34 )
Would it be possible to consider adding this permission line to the manifest in a future update?
It wouldn't affect normal users since it remains ungranted unless an ADB command is used, but it would be a huge lifesaver for Android 17 users who need cross-profile routing.
Thank you for your time and all the hard work on this project!