This weeks Android issue

[ecramp]

Wigle started up and stalled this morning saying that it was "Waiting for GPS" - turns out that Google seems to have decided that I need to give permission for Wigle to access my location, something that has not been an issue in years. I went to the Google location setting and it displayed a new list of all Googles apps that seem to automatically have permission, once I added Wigle to the list it's all working. Sorry, it's my fault for letting Google update my phone.

[arkasha]

unusual - the app should request permission explicitly (and modally) if it can't use the GPS.

if you wouldn't mind sharing, (feel free to use PMs/email), with what Android versions and device did you see this problem?

[ecramp]

It's a Pixel 3, it was running Android 10 but it updated to Android 11 this morning. After I headed into work I turned Wigle on, driving my normal route, and every device and AP that I passed showed up as a "new" device! I thought that the upgrade had deleted my database but when I arrived at work I took a couple of screenshots to illustrate this for you and uploaded - the upload is 20200909-00165 and the numbers shown in the upload make sense. I'm attaching the screenshots to illustrate this.

Attachments

Screenshot_20200909-073229.png (109.67 KiB) Viewed 38809 times

Screenshot_20200909-073214.png (139.29 KiB) Viewed 38809 times