Only the newest radar tiles that are missing on the phone are downloaded. But it reloads all the data on to the map after the download. There might be a problem with the newest download that causes the blanking??
It’s difficult to find a bug that is sporadic and hard to replicate. Essentially, I figure out what is happening over time from all the clues.
Yay, good news guys. I caught the bug in the wild today with the debugger and found the cause. It’s a silly oversight by myself and will be fixed in the next release.
It took me a few days of trying to catch it, essentially I needed to leave radar for more than 24 hours to catch it.
I get a working radar overlay for awhile after a new version, and then it degrades over time until it isn’t there anymore.
One thing I noticed during the “degrades” step was that toggling the indicator for radar, down in the bottom row, would move the now-line back to whenever the most recent radar data was, but it wouldn’t show anything. Manually move the now-line into the past and it would show. (For awhile. It has stopped doing this.)
Rebooting, forcing data reset, etc. don’t affect this; getting a new version of the app installed does.
Hi @Ohan, I use the coverage map with the radar but the coverage generally doesn’t change much over time so I only update the coverage on the server every hour and in the app after the file is a day old.
The bug occurred because when a tile loaded the coverage file it would ask how old it was. If it was older than a day, it would send a request to the downloader to download the coverage file and wait for the file to be downloaded. The problem is that the download also asks whether the file needs downloading, just in case it’s already downloaded but this used a different piece of code which said it didn’t need downloading. So the tile kept waiting for the coverage file to download and never loaded.
This is why it takes at least a day for the bug to happen.
I’ve fixed it to use the same code now. My code is pretty messy and needs tidying.
I just emailed a debug-log since forced update is sometimes still needed.
Sometimes I’m experiencing that after a (single manual) refresh was performed, both a single tap and a double tap on the time digits would lead to displaying different times, but none of them showing radar. Radar was however viable if swipeimg a little to the left to an earlier time.
When I did a “double” refresh = forced refresh, and then the double tap on the time then this would lead to radar data being shown.
It seamed defenetly like it tired to “show the last time with available radar data” when dubbeltapin the time, but that the data was not there.
After a forced refresh, moments later it worked for the same time, and I did not shance the timezone in between, nor the zoom. So there was. Definitely radardata at that time and place that was suppose to be displayed. And I did manual (single tap, non forced) up data multiple times, and waited longer than what’s normally needed. So if it was downloadimg and displaying it should hane had enough time to so.
I wounder, @duane, if the part of the code that’s executed then dubletaping the time just checks the timestamp for the latest avaliable radardata, of it also checks if it (correctly) have been downloaded?
(Perhaps a checksum could be good on downloaded (radar) data to compare and see if it became corrupt or only partially downloaded?)
I’m finding that this only happens if Flowx is left on in the background for a while (but it’s definitely not needed to wait 24 h). Then when the app is brought back from the list of apps running in the background the radardata is not refreshed automatically, nor on normal manual refresh. Only forced refresh will result in the latest, radar being downloaded. (*)
If however the app is closed and reopened, then the latest radar data is downloaded without the need to do manual refresh at all (normal nor forced).
(*) Perhaps the behavior here is dependent on Android settings for what/or how many apps are allowed to do what in the background?
The time is different because the latest radar image is not current. It’s at least 10 minutes old. This is the amount of time it takes to capture the radar image, processing it, and your app downloading it. It’s very difficult to get the current image immediately.
It seems the original bad bug is fixed but it sounds like there is another bug there. Like the last bug it might take time to find and fix since we don’t know a way to easily replicate it.
Wait more than 10 min or so. (I guess untill the manifest says that there is new radar data awailable.
Re-open Flowx from list of apps running in background. (Don’t zoom in/out, don’t change location and don’t do forced refresh.)
Togle between double taping and single taping on the time. Notice the lac of radar data displayed in both cases.
(I’m guessing that the time being displayed when dubletaping on the time is the time of latest available radar data, according to the manifest, but that the radar data is not being displayed since it was not downloaded automatically yet, while Flowx was in the background, or that the data it corrupted, incomplete, or the download was set to lower priority by the android system while Flowx was in background.)
Do a forced refresh, or close Flowx and restart it.
Togle between double tap and single tap on the time. Notice that double tap will display about 10 min old radar (as it should, since it s the latest avaliable) , and that single tap will display current time, without radar.