Unable to load new content at the moment...
Hi,
Sometimes when I minimize Primal for a long time then I restore it, show this message: Unable to load new content at the moment...
But If I close and open Primal again, the message disappear and show new notes.
Its not a bug, it means that the app couldnt load notes at that moment - 2nd line shows the error message. As soon as the app succeeds to get recent notes, it removes the error.
The question is if we should show the error message or silently ignore and not show anything.
The question is if we should show the error message or silently ignore and not show anything.
Show a message like "loading new content"?
As soon as the app succeeds to get recent notes, it removes the error.
In my experience I always needed to restart Primal to the message disappear and show new notes.
This is an error message. App tried loading new content and couldnt reach the api 3 times in a row. Now app waits next sync cycle in 25-35 secs. When you exit/enter you restart the sync cycles from the start.
I want to implement pull to refresh first before making any further changes to the feed sync. Except pagination issue which is still blocked by backend.
Retry button with the error message might also be the solution.
Second the report here; message pops up often, has become an annoyance when mobile. 'API unreachable at the moment' sounds worse than just not finding newer notes, in my opinion. Was this introduced with latest release (v0.95.4)? Don't recall having this happen in prior release, what is the logic behind it?
Silently ignore, not show anything and implement pull to refresh both sound great. Only workaround for the time being is to force close and reopen application?
Don't know if related but I've been getting a lot of 'Unable to like. Please try again later.' pop-up messages (phrasing might be different, but still,) could that be related to my relays or the application? Has been happening for 3-4 days.
Edit: Curiously enough, tested and it happens on mobile, Primal Web (desktop) works just fine.
I'm not seeing this anymore. If I reproduce again, I can reopen.