Post

Replies

Boosts

Views

Activity

Reply to Did iOS 26 break geolocation for PWAs?
We’re seeing very similar behaviour with Big Rigs Camp Finder, an installed Home Screen PWA. Current real-device results on iOS 27: • Geolocation works correctly in Safari. • The installed Home Screen PWA also works when iOS allows access. • However, iOS periodically presents the native location permission prompt again even after location has previously been allowed and working. • We have also seen the Home Screen PWA become stuck returning PERMISSION_DENIED while Safari continued to work. • Reset Location & Privacy restored the existing installed PWA without reinstalling it, but the repeated permission prompt later returned. • We added diagnostics and repeatedly captured this state in the Home Screen PWA: getCurrentPosition(): success navigator.permissions geolocation: denied display-mode: standalone geolocation available: yes So the Permissions API state does not reliably reflect the actual result of the geolocation request in this context. Our implementation is user-gesture driven: • no geolocation request on app startup or mount • getCurrentPosition() only after the user taps Locate Me • watchPosition() starts only after the one-shot request succeeds • no automatic retry loops or polling Safari remains stable while the standalone Home Screen permission behaviour is inconsistent. Happy to provide screenshots, timestamps, or further reproduction details if useful.
2w
Reply to Did iOS 26 break geolocation for PWAs?
We’re seeing very similar behaviour with Big Rigs Camp Finder, an installed Home Screen PWA. Current real-device results on iOS 27: • Geolocation works correctly in Safari. • The installed Home Screen PWA also works when iOS allows access. • However, iOS periodically presents the native location permission prompt again even after location has previously been allowed and working. • We have also seen the Home Screen PWA become stuck returning PERMISSION_DENIED while Safari continued to work. • Reset Location & Privacy restored the existing installed PWA without reinstalling it, but the repeated permission prompt later returned. • We added diagnostics and repeatedly captured this state in the Home Screen PWA: getCurrentPosition(): success navigator.permissions geolocation: denied display-mode: standalone geolocation available: yes So the Permissions API state does not reliably reflect the actual result of the geolocation request in this context. Our implementation is user-gesture driven: • no geolocation request on app startup or mount • getCurrentPosition() only after the user taps Locate Me • watchPosition() starts only after the one-shot request succeeds • no automatic retry loops or polling Safari remains stable while the standalone Home Screen permission behaviour is inconsistent. Happy to provide screenshots, timestamps, or further reproduction details if useful.
Replies
Boosts
Views
Activity
2w