@Eugene I guess this is one for you.
Summary of the Issue
When sending regular data (every 10 seconds or so) to the terminal widget from hardware, the widget behaves as expected.
However, if the data is sent less frequently then then when the the iOS device is screen locked, left for a few minutes, then unlocked again, the data in the Terminal widget is repeated - sometimes multiple times.
Putting the Blynk app into edit (stopped) mode then immediately back into run mode restores the terminal widget data to what it should be - without the duplicated lines of data.
This screenshot shows the duplicated data…
and this shows the same data after the widget has neen stopped and started again…
Based on testing with several users, the issue appears to affect both local and Blynk cloud servers and the current iOS app version of 2.25.0 (3) and the beta version of 2.26.0 (2).
The data that’s being repeated isn’t being sent multiple times. It seems that when the app ‘wakes up’ from ruining in the background some sort of refresh refresh from the server is being done, which seems to be causing the problem.
It seems that the issue was raised here, over a year ago, but the description of the problem wasn’t very detailed:
This thread has much more detail, although it began by raising two issues then by about post number 38 began focusing on this duplication of terminal data in more detail:
This latest topic is a bit of a time-consuming read, but includes code that can be used to replicate the issue.
Both @877 and myself have almost identical results, so it seems it’s fairly easy (if a little tedious because of having to wait for a few minutes each time) to replicate.
If you want any assistance with testing a beta fix then I’d be happy to help.
Over to you…