Skip to content

React-native Firebase Remote Config never use cache #4781

Answered by mikehardy
n10ty asked this question in Q&A
Discussion options

You must be logged in to vote

Have you confirmed from the firebase console that you are indeed fetching more than expected? i.e., do you really have a problem?

I think that is just a misunderstanding of the source value.
It came from remote so I believe it will always say it is from remote even if it is not refetched
If the fetch never happened, I believe it would be from default or local
You don't indicate what the fetch methods return to you, if you carefully examine the return values of the various fetch / activate methods (and perhaps use the ones that are single actions, not multiple actions) you may find it is behaving as expected

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@n10ty
Comment options

@mikehardy
Comment options

@n10ty
Comment options

@mikehardy
Comment options

Answer selected by n10ty
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants