Walter, et. al.,
Noticed two small errors and one misleading alert last night while flying with the production 7.5.20 software.
1) Screen draw error. For some reason, while in follow-plane mode, a small region in the lower left corner spontaneously failed to draw correctly for about a minute or so. It lasted long enough for me to pull out my phone and snap a pic, but not long enough for me to turn off the flash and snap a second one. (I.e., it eventually fixed itself without me touching anything.) I should have the detailed GPS log from this flight, if that would help with troubleshooting.
2) TAF decode error. While checking weather at the home drome, I noticed that the decoded TAF did not include the times for the various "Becoming..." sections. Note in the raw text that the times are present, so there appears to be an error in your decoder parsing logic.
3) ADSB Alert "error". During flight, I got an iFly Alert telling me that the ADSB signal was lost. When I went to Mode, the report was that I had ADSB Live Weather, but no signal. Normally, I would expect that to be a problem I can't solve, as the message indicates there is good comm between the iFly and the SkyRadar, but the SkyRadar is not receiving a signal from the FAA ground station. However, I didn't believe it, and power-cycled the SkyRadar. The iFly "immediately" (within several seconds) reported that it was in ADSB Live Weather mode, and I again had timely weather reports available. Of course I don't know what low-level communications cues you're using to diagnose and report errors, but I was disappointed that the iFly did not correctly diagnose and report the problem in a way that would more clearly indicate a SkyRadar power cycle was required.