No. The only time I've seen this is if the ADSB data stops coming in (which does sometimes happen for various reasons). The first indication of this is that ADSB targets will grow "noses" (a long thin line straight oft the point of the arrowhead target), and then start traversing these lines. That's telling you iFly doesn't have current ADSB traffic data for live updates, and is propagating the target's expected movement based on last known course and speed. If the target reaches the end of its line before live ADSB data comes back, then it's erased from the screen. (I think the lines are sized to last ~15-30 seconds or so).
What are you running iFly on, and what version are you running? What ADSB-in device are you using?
The iFly team is pretty focused on development of the new EFB software, so your report may not get a lot of traction, but if you want any chance of getting their attention you'll need to provide them with data to look at. Go to Menu > About > Connected Devices > Select Wireless Device, and check "Enable ADS-B Logger", and fly around until the problem happens, and keep flying for a little while (to see if it comes back, or to "prove" that the problem persists for a while, and collecting data either way). When you think you've captured enough data to demonstrate the problem, you can shut down and restart iFly.
After you're back on the ground and are able to send emails from your device, launch iFly again and choose Menu > About > Send Bug Report > Select Log, and scroll down to find the ADSB log corresponding to the flight where you collected the data (the name will be in the format "Adsb_2022_mm_dd-hh.mm"). iFly will auto-generate a bug report email and attach the log file, and give you the option to write some information in the body of the email before sending it.