Android now stops you sharing your location in photos

What happened

It has been reported that Android now prevents web apps from receiving the geolocation (EXIF) metadata embedded in photos, a change that has blindsided small sites such as OpenBenches — a niche project that maps memorial benches from user-uploaded photos. Developers used to rely on the simple HTML file input () to open the phone’s photo picker and preserve EXIF. Then, allegedly, Google nudged sites toward a generic file picker (), and later tightened things further so even that route no longer delivers location metadata to the browser. Progressive Web Apps, Bluetooth/QuickShare transfers and direct email shares reportedly strip the location too. The only surefire way left, apparently, is to plug the phone into a computer, copy the file and upload from a desktop browser. Frustrating? Absolutely.

The developer angle

Why does this matter beyond a small annoyance? Because it breaks workflows and pins extra cost on tiny operators. The OpenBenches authors say users flooded their inbox blaming the site for “breaking” uploads — the human fallout is real. It has been reported that the author argued Google’s motive is privacy: people often don’t realise their photos carry precise coordinates and platforms have valid reasons to reduce accidental oversharing. Many large social services already strip EXIF by default, so you can’t blame the safety-first instincts. But the change also came, allegedly, with little or no community consultation or advance notice, which leaves developers in the lurch. That’s the emotional key: users think the service is broken; maintainers get the blame; nobody is any safer — except that the data is harder for small, legitimate projects to use.

Fixes and fallout

What now? The blog suggests the only reliable path may be building a native Android app (and perhaps an iOS one), because apps can request explicit permissions to access image metadata — at a cost in time, money and maintenance. Other ideas floated include a browser permission prompt like “This site wants to read photo locations: Yes/No,” or pushing for HTML spec changes; the author even asked readers to +1 a spec comment. This joins a broader trend of platforms tightening metadata access in the name of privacy. Helpful? Yes. Messy for developers? Also yes. If you’ve got a working workaround for preserving EXIF in browser uploads on Android, the community is listening — drop a comment, and maybe we can cobble together something that doesn’t require everyone to become an app shop overnight.

Sources: shkspr.mobi, Hacker News