Just noticed that this is still happening (and it's happening right now since we are at the end of month again...).
Looking at the code, it seems that the issue comes directly from the server side. The server returns a ux: null in the trend array after metar which is why all the wrong time have exactly the same value, howOld treated it as 0... The returned time is in fact the time since Unix epoch....
Hi @Zelinnov, you mean a different user account, right? Please check this link first and then let me know; ideally you should contact me directly from your email address that is associated with the account you refer to.
All the best ~ Marie
You should at least show a screenshot of the area where you have observed this « error ».
Sometime winds are not matching the isobars because the isobars don’t refresh concurrently with the wind direction (seen on iPad). If you change the model there are synchronised again.
@LLXC please check if you are using the same weather model on both devices and also check the altitude set to surface. If you experience it again send me screenshots of both devices and also the exact location. Thanks!