Repository navigation
|
How can a team catch Local network access without the ACCESS_LOCAL_NETWORK runtime permission automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rqn 'NsdManager\|MulticastSocket\|_tcp\.local\|mDNS' {A} . && ! grep -rqn 'ACCESS_LOCAL_NETWORK' {A} .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. From Android 17 enforcement is mandatory for apps targeting API 37 or later. mDNS, NSD discovery, multicast, and direct LAN connections fail with a security exception unless the app declares and requests ACCESS_LOCAL_NETWORK. The fix. Declare android.permission.ACCESS_LOCAL_NETWORK, request it at runtime before any LAN discovery or connection, and degrade gracefully when denied. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-LOCAL-NETWORK-PERMISSIONwith a coverage line and a proper exit code.What the hit means. From Android 17 enforcement is mandatory for apps targeting API 37 or later. mDNS, NSD discovery, multicast, and direct LAN connections fail with a security exception unless the app dec…