Thanks for the logs. In the first log I don't see any Traffic Reports for 7ME. But also there are no bad packets or indications that the ADSB data was corrupt or missing in any way. It appears the traffic simply was not transmitting, or was not reporting as 7ME. So unfortunately this didn't shed any light as to why it's working in the other app.
In the 2nd log I see 7ME fly the pattern at BXK, then fly south, we stop getting messages for several minutes, reappears flying toward GYR, lands and (expectedly) no more messages. The "gap" occurred when the aircraft was some distance from your ship, and low, so this doesn't seem to be the scenario you are describing.
If there is an ADSB message that is being interpreted incorrectly by our system, then we will need to go through the stream byte by byte. I know this might be a difficult request, but might be the only way: If you can start the recording as soon as you observe the traffic is missing, but is showing on another system (using the same ADSB device of course), let it run for 60 seconds, then stop the recording. This might allow us to find the error, if one exists. But, it's possible this is just normal behavior - if iFly doesn't receive a target's message for 60 seconds we remove that target from the screen. It's possible FF simply keeps showing data & projecting location for a longer period of time.