Replies: 2 comments 1 reply
-
Solved, for anyone having the same situation : my try catch ended before because I obviously forgot to await for what I have been trying to catch. |
Beta Was this translation helpful? Give feedback.
-
Reopening because the implementation I made actually doesn't throw error but doesn't work either. First, what is said implementation?
By this:
The issue now is that the provider doesn't seem to actually invalidate at all. what actually happens: Would like some help on this one. |
Beta Was this translation helpful? Give feedback.
-
I want to implement a pull to refresh. On all example I have seen with riverpod, the recommended method is:
The issue with this method while used on my provider:
wherea in any other cases (fail on first load, fail when provider is not listened anymore and then getting listened again, etc), this same exact error is handled perfectly by riverpod.
But based on this:
I think the issue is about the future in:
However, I don't know how to catch it, a simple wrapping of this in a try catch block doesn't work, the code never goes to the catch block and the error still throw.
Would love some insight.
Beta Was this translation helpful? Give feedback.
All reactions