Android 17 blocks your app from the store's printer by default. Choose a picker or file a declaration
If your Android app talks to a receipt printer, a scale or a kitchen screen over the shop's Wi-Fi, Android 17 will cut that connection the day you target it. Google Play now wants a declaration before it lets you ask for it back.

Apps that target Android 17 (API 37) lose local network access by default, including mDNS discovery, raw sockets to local addresses and .local names, through every networking library. There are two ways back: a system picker, where the user chooses one device and no permission is needed, or the new ACCESS_LOCAL_NETWORK runtime permission, which Google Play now restricts to core functionality and requires a Play Console declaration for. Store and kitchen apps should pick a path before they raise their target SDK.
What Android 17 turns off
Android 17, API level 37, adds a protection that most store and restaurant apps will feel. When an app targets API 37, its access to the local network is blocked by default.
The Android developer documentation spells out what that covers. Raw sockets to local addresses, mDNS and SSDP discovery, and NsdManager are all affected, and so is every networking library on top of them, including OkHttp and Cronet. Resolving a ".local" hostname needs the permission. Traffic from a WebView inherits the host app's permission, so an embedded web page can't route around it. One exemption: if the device's DNS server is on the local network, DNS traffic on port 53 still works.
On October 29, 2026, Google Play added a policy on top. The new Local Network Permission is restricted to apps that need it for core functionality "when device pickers are insufficient," and apps targeting API 37 or higher must submit a Play Console declaration to use it. Developers have at least 30 days from October 29 to comply. Check the Policy Deadlines page for the exact date that applies to you.
Apps targeting API 36 or lower keep local access, which is granted implicitly with the INTERNET permission. Google says not to add the new permission to those apps. So nothing breaks today. It breaks the day someone raises the target SDK, which Play eventually requires.
The store this lands in
Think of an ordinary shop or cafe running on Android: a point-of-sale tablet, a staff phone app, maybe a customer kiosk. The app talks to things on the store Wi-Fi:
- a receipt printer, found by mDNS or a fixed IP
- a label printer in the back room
- a scale on the counter
- a kitchen display or order screen
- a cash drawer through a network bridge
- a local server or hub that syncs when the internet drops
Every one of those conversations is local network traffic. On API 37, without one of the two paths below, they stop.
The question isn't whether you need the network. It's whether your app needs one device the staff can pick, or the whole room.
The question isn't whether you need the network. It's whether your app needs one device the staff can pick, or the whole room.
Path A: let staff pick the device
Android's first answer is a picker. Instead of the app scanning the whole network, the system shows a dialog and the user chooses a single device for the app to use. For mDNS discovery, NsdManager has a DiscoveryRequest with FLAG_SHOW_PICKER. Addresses chosen through the picker can be used without the broad permission. For media, apps using Output Switcher as their picker don't need the permission either, and Google says more casting guidance is coming.
This suits a lot of store setups. A staff app that prints receipts to "the front counter printer" needs one device, chosen once at setup. The picker is also the honest version of what the app is doing, and Play's policy clearly prefers it.
What to plan for:
- A setup step. Somebody picks the printer the first time, and again whenever the printer is replaced. Put that in the onboarding flow and the troubleshooting screen.
- Devices that don't advertise. If your printer only works on a fixed IP and doesn't announce itself over mDNS, the picker may not find it. Test with the hardware your customers actually own.
- More than one device. A kiosk that drives a printer, a scale and a display needs each picked. That's fine at setup, but clumsy if the app has to rediscover them often.
Path B: ask for the whole room
The second path is the new ACCESS_LOCAL_NETWORK permission. It sits in the NEARBY_DEVICES permission group. You declare it in the manifest and request it at runtime before you touch the local network. Google describes this path as being for complex cases, such as home automation or managing IoT devices, that need broad, persistent access.
Some store apps fit that description. Think of a back-office app that monitors every printer and terminal in a store, or a hub that keeps several devices in sync without staff choosing each one. For those, a picker really is insufficient.
What it costs you:
- A Play Console declaration. You'll need to explain why the permission is core to the app and why pickers aren't enough. Write it the way a reviewer would read it: what the app does, which devices it talks to, and why a person can't pick them one at a time.
- A runtime prompt. Staff will see a permission dialog. If they deny it, the app needs a clear fallback and a way to try again, ideally from a settings screen and not a dead end.
- Review risk. If the declaration is thin, the update can be held. Build that time into your release plan.
Remember the WebView rule here too. If part of your app is a web dashboard shown in a WebView, such as a kitchen screen served from a local hub, it inherits whatever local network access the app has. A picker grant for one printer won't cover a web screen that talks to a different device.
Decision guide
Picker or permission
| Consideration | Path A: system picker | Path B: ACCESS_LOCAL_NETWORK |
|---|---|---|
| What the user sees | A dialog to choose one device. | A runtime permission prompt |
| Play declaration | Not needed. | Required for apps targeting API 37+ |
| Good fit | One receipt printer, chosen at setup. | A hub managing many changing devices |
| Watch for | Devices that don't advertise over mDNS. | Denied prompts and a thin declaration |
Deciding before you raise the target SDK
Here's how we'd walk a store app through it:
- List every local connection the app makes, including the ones a third-party SDK makes for you. Printer and payment SDKs often do their own discovery.
- Mark each one : one device chosen once, several devices chosen once, or devices that change without anyone choosing.
- Use pickers wherever the answer is "chosen once." That's most receipt printers and many scales.
- Request the permission only for what's left , and write the declaration around those cases.
- Test on an Android 17 build with the target raised against real store hardware, including WebView screens and any vendor SDKs.
- Ship the setup and troubleshooting screens before the change , so support isn't learning it from customers.
If you sell the app to other businesses, tell them early. A store owner who updates the app and sees a new prompt, or a new "choose your printer" step, during a Saturday rush will call support. A short note in the release notes and an email to account owners makes the change feel planned rather than broken.
We made a similar case for Android's one-tap location button in an earlier note: the narrower, system-mediated option is usually the better product, as well as the easier review.
If your Android app runs a store, a kitchen or a warehouse floor and you'd like help deciding which path fits, our mobile applications team works on exactly this kind of hardware-facing app. Get in touch and tell us which devices your app talks to.
Related work: Spin Market.
How the work moves
Before you raise the target SDK
- List local connections
Include third-party SDKs.
- Mark how each device is chosen
Once, several, or never by a person.
- Pickers first
For anything chosen once.
- Permission for the rest
Write the Play declaration around it.
- Test on Android 17
Real hardware, WebViews, vendor SDKs.
FAQ
What is the Android 17 local network permission?
When an app targets Android 17 (API 37), access to the local network is blocked by default. That covers raw sockets to local addresses, mDNS and SSDP discovery, NsdManager, ".local" hostnames, and traffic through libraries such as OkHttp and Cronet, including WebView traffic that inherits the host app's permission.
Do I need ACCESS_LOCAL_NETWORK for a receipt printer?
Not always. Android's picker lets staff choose a single device, and addresses chosen that way can be used without the broad permission. A staff app that prints to one front-counter printer, chosen once at setup, is the kind of case Play's policy prefers to handle with a picker.
When do I need ACCESS_LOCAL_NETWORK, and what's the Play declaration?
ACCESS_LOCAL_NETWORK is for cases that need broad, persistent access, such as a back-office app that monitors every printer and terminal. On October 29, 2026, Google Play restricted the permission to core functionality when device pickers are insufficient, and apps targeting API 37 or higher must submit a Play Console declaration. Developers have at least 30 days from October 29 to comply; check the Policy Deadlines page for the exact date that applies to you.
Does this affect apps that don't target Android 17 yet?
Apps targeting API 36 or lower keep local access, granted implicitly with the INTERNET permission, and Google says not to add the new permission to those apps. Nothing breaks today. It breaks the day someone raises the target SDK, which Play eventually requires.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.