[Feature Request] Please add `INTERACT_ACROSS_USERS` permission for Android 17 cross-profile routing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.1k
- Forks
- 4.6k
- Avg merge
- 19d 15h
- Merged PRs (30d)
- 1
Description
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: https://github.com/VentralDigital/InterProfileSharing/issues/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!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AndroidManifest.xml used by the Android build and read how permissions are currently declared. Add the requested permission declaration, then verify that the generated Android manifest includes it and that the project still builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100