I think you may have a reasonable point about alerting the user to areas where radar data has been lost, if that can be detected. You seem to know something about how the datastream is formatted; I do not, so I don't know if that's easily implementable or not.
At the risk of offending you, I will mention again (because it wasn't clear from your previous post) that for the AP folks to fully engage and dig into what you are seeing specifically with radar data, they will need the *ADSB* data log, not just a standard bug report. While iFly automatically logs quite a bit of app performance data every time it runs, ADSB data is NOT captured by default. You need to turn on ADSB logging *before* you see the issue...or at the least, while the issue is still occurring. The instructions for how to do that are in my previous replies.
FYI, once recorded, log files persist for some time (indefinitelyd until manually deleted?). If you have trouble sending a log, you can try again...it's not a one-shot thing.
Also, please know that the auto-generated email created by the "send bug report" feature always includes a substantial text component in the body of the message, as well as attaching the log file. So while I've never seen the "gmail app error" message you alluded to (what was the exact text?) and that could be an actual issue, your coment that it "instead pasted the current session log file into the message body" is simply a misunderstanding of how the bug report email is normally generated.
What type of device are you using? (Android, iOS, Windows?) For Android and Windows, if necessary I can help you to manually navigate to the folders where the log files live and you can use whatever email app you like to attach the file. (I'm not an iOS guy and don't know if or how you can manually search for the log files on those devices.)