Reported by @lukaszkucinski, I wasn't able to reproduce.
The most likely scenario is that:
Client thinks there's no user data and asks backend for a refresh.
Backend sends data to client.
Backend receives the query to refresh but sees that there's nothing to update.
Client waits for the backend reply that will never come, hence continuously displaying 'Loading'.
If that indeed is the case then the easiest solution would be to always update meta.timesUpdated on the backend, even if no real update takes place. Alternatively to alleviate the issue we could delay the initial refresh on the client by a couple seconds, though that's not ideal as would delay the initial update for all new clients.
Reported by @lukaszkucinski, I wasn't able to reproduce.
The most likely scenario is that:
If that indeed is the case then the easiest solution would be to always update
meta.timesUpdated
on the backend, even if no real update takes place. Alternatively to alleviate the issue we could delay the initial refresh on the client by a couple seconds, though that's not ideal as would delay the initial update for all new clients.