-
Notifications
You must be signed in to change notification settings - Fork 787
MockedProvider does not return data when fetchPolicy is set to "cache-and-network" #779
Comments
Thanks for filing an issue @eskimoblood. Would you be able to provide a reproduction of this using the react-apollo-error-template? |
This issue has been automatically marked as stale becuase it has not had recent activity. It will be closed if not further activity occurs. Thank you for your contributions to React Apollo! |
Same issue. Try mounting a |
This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo! |
I'm also having this issue, I get:
When using 'cache-and-network' as fetchPolicy. |
Can you provide a reproduction we can run please? |
This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo! |
This issue has been automatically closed because it has not had recent activity after being marked as no recent activyt. If you belive this issue is still a problem or should be reopened, please reopen it! Thank you for your contributions to React Apollo! |
not a complete reproduction, but
logs twice:
when changing to:
it logs the second time:
|
Any update on this issue? |
I'm having this problem too when trying to update the cache with a MockedProvider. |
I'm also running into this issue when using a |
The same to me |
Any way to get this issue re-opened? I'm seeing it too when using |
MockedProvider does not return data when fetchPolicy is set to
cache-and-network
. When removing the fetchPolicy part from mygraphql
call, the test data are returned.Version
The text was updated successfully, but these errors were encountered: