iOS Location dialog message is not displayed for every fresh install |
||||||||
Issue descriptionApp Version: 61.0.3163.16 iOS Version: 11.0 Beta 4 Device: iPhone 7, iPad Mini 2 Steps to reproduce: Perform Fresh install of Chrome Launch Chrome Accept ‘Terms & Conditions’ Sign in to chrome Opens up a NTP Observed results: iOS Location dialog message is not displayed and location is enabled for chrome in device settings Note: App is deleted by long press on Chrome icon then tapping on cross icon. Need to reset(Settings>General>Reset>Reset Location) location settings on device to get location prompt on chrome app again If the ‘iOS location dialog’ message appears for the first time, remove the app and reinstall it, it will not show iOS location prompt again. Expected results: iOS Location dialog message should be displayed as ‘Chrome Would like to use your current location’ after every fresh install Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: Not Tested Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build : M60, Yes Bug reproducible on the current beta channel build : M61, Yes Type-bug-regression? No Link to video: https://drive.google.com/open?id=0B6nZ3QPCkSVcbV96LUNJQUIwYms
,
Aug 3 2017
,
Aug 4 2017
Hi Liaoyuke, I tried either ways, it shows location prompt after the location reset.
,
Aug 7 2017
,
Aug 16 2017
,
Aug 16 2017
,
Aug 16 2017
I wonder if this is a feature that iOS11 remembers your location choices. stk@ can you take a look? Marking as ReleaseBlock since it needs investigation incase it is covering a larger issue with location and privacy.
,
Aug 17 2017
it seems like the iOS 11 location dialog decision persists between reinstalls, as per original bug description. I don't think I am the right owner and I'm not sure what needs to be done, if anything.
,
Sep 6 2017
justincohen@ please what's the status on this blocker? We aim to fix our blockers as early in the cycle as possible.
,
Sep 7 2017
I doesn't look like there's anything to be done here. iOS11 persists this now. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by liaoyuke@chromium.org
, Aug 3 2017Owner: subhashi...@chromium.org
Status: Assigned (was: Untriaged)