All Sensor data fails to display on map, android 13

User Experience Bug Reports
1

On my new Samsung A14 G5 with android 13 all sensor data fails to display on the map.
There are no numbers at all inside the circles on the map.
This is a display formatting issue in android 13 as the WEB map clearly has access to the data base data for if you click on a blank circle the web page then correctly opens and shows the sensor reading history chart.
I have tried chrome, fire fox and fire fox focus. All show the exact same issue with blank circles with no numbers inside.

2

Bob, I have the same problem on my IPad. I switched to the airquality app and choose the purple air function at the bottom. I am a Luddite so hopefully someone else will chime in.
W

3

Are you using monthly or yearly averages with the “Show averages as rings” option selected? There’s currently a bug with those settings selected that causes the circles to be extremely small and black colored. This can obscure the numbers.

If that isn’t the problem you’re experiencing, does the issue still persist when using different data layers and averaging periods?

4

I overcame the issue by installing default on the phone and then reinstalling everything, a very painful process. It seems my new service provider ran some scripts when their new Sim was installed with the result much of the phones operation had become strange. Starting from zero sorted out all sorts of odd issues.

1 Like
5

Any chance of getting this bug fixed? It’s been a while. I’m getting the issue on all browsers and operating systems including Firefox and Chrome in desktop Windows. (Unchecking the “Show Averages As Rings” box does fix it, so a good short-term fix could just be making it the default for this to be unchecked, but presumably you eventually want to get both options to work)

I’m also willing to try to fix it myself you guys use something that allows pull requests.

1 Like
6

Thank you for specifying the browsers and operating system you used. The map isn’t currently open source, but we’ve fixed this in a recent update.

Please let us know if the issue still occurs or if you find anything else.

2 Likes
7

Thank you kindly sir Josh