You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intended outcome:
Being able to refetch on a query without fetchPolicy defined.
Apollo-Client - 1.1.1
React-Apollo - 1.1.1
How to reproduce the issue:
Try to refetch a simple query.
Am getting the following error:
If I use 1.1.0 of Apollo Client - the refetch works as intended.
Appears this fix - Fix: Remove ability to set default fetchPolicy, which broke polling queries PR #1630
Has broken the ability to refetch a simple query.
Thanks for the help!
The text was updated successfully, but these errors were encountered:
@harmon25 Thanks for reporting the issue, it's very odd. Reverting that PR should not break anything that wasn't broken before. In addition, we have tests for refetch. I would think it much more likely that 1.1.0 has broken refetch. Are you sure about the version that you're running? Sometimes there can be multiple versions installed, for example one directly, and one through react-apollo.
In any case, would you be able to put together a quick reproduction using the error template if the error persists? That way I can debug it.
Hm OK does appear having both apollo-client and react-apollo as dependencies is unnecessary and possibly causes some weird behaviour. Not really the problem though, more to do with fetchPolicy set to cache-only after unmount - which is what is happening in my application...
Intended outcome:
Being able to refetch on a query without fetchPolicy defined.
Apollo-Client - 1.1.1
React-Apollo - 1.1.1
How to reproduce the issue:

Try to refetch a simple query.
Am getting the following error:
If I use 1.1.0 of Apollo Client - the refetch works as intended.
Appears this fix - Fix: Remove ability to set default fetchPolicy, which broke polling queries PR #1630
Has broken the ability to refetch a simple query.
Thanks for the help!
The text was updated successfully, but these errors were encountered: