endless looop upon react render when suspend: true
See original GitHub issueSince version 0.4.0 I am getting an infinite loop on startup of our app. 0.3.1 works fine, but 0.4.0 and 0.4.1 are ending in this loop:

my component uses the simple useQuery call.
Note this does not occur when I manually handle loading states-only when suspend: true is passed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
3 ways to cause an infinite loop in React - Alex Sidorenko
React limits the number of renders to prevent an infinite loop. Here are 3 potential causes of the infinite loop in React.
Read more >"Error: Too many re-renders. React limits the number of ...
The reason for the infinite loop is because something (most likely setState ) in the event callback is triggering a re-render.
Read more >How to Solve the Infinite Loop of React.useEffect()
After initial rendering, useEffect() executes the side-effect callback that updates the state. The state update triggers re-rendering. After re- ...
Read more >5 useEffect Infinite Loop Patterns | by Naveen DA
It is good to know the infinite loop patterns of React. ... React which is “When state or Props is changing, the component...
Read more >Preventing infinite loops in componentDidUpdate() ✏️
ComponentDidUpdate() is prone to infinite loops. To prevent this problem, pass prevProps and prevState to componentDidUpdate(), compare them ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@capaj Could you please provide a reproduction on https://codesandbox.io? As a source you can use https://www.graphqlhub.com (GraphQL API url: https://www.graphqlhub.com/graphql, example query here).
We’re having the very same issue now. It started to happen after we dropped IE11 support for our codebase, removed babel-polyfill, fetch polyfill and transform-regenerator. We’re still investigating what’s happening.