Solvedag grid reactNext - React Component '...' not created within 1000ms**

I'm submitting a ... (check one with "x")

[x] bug report => see 'Providing a Reproducible Scenario'
[] feature request => do not use Github for feature requests, see 'Customers of ag-Grid'
[] support request => see 'Requesting Community Support'

Providing a Reproducible Scenario
https://plnkr.co/edit/EcryNGfNAWqKd5X2Yzvo?p=preview

Current behavior
After quick grid mount/unmount (reactNext) with custom renderers errors like 'React Component '...' not created within 1000ms' are occured

  • ag-Grid version: 21.0.1
  • ag-grid-react version: 21.0.1
52 Answers

✔️Accepted Answer

Does this issue really fixed? I upgraded to 21.1.0 got no luck. Still plenty of errors saying "ag-Grid: React Component ... not created within 1000ms"

Other Answers:

@seanlandsman It may have fixed an issue, however mine was still happening but I realised it's because of the return null - AG thinks the component hasn't rendered. I've change it to this now and it works:

function roadmapLinkRenderer({ value }) {
  if (!value) {
    return ''; // null breaks AG's logic to determine if component is rendered.
  }

  return (
    <Link to={`/roadmap/${value}`} title="Explore in Roadmap">
      <FaAlignCenter size="18px" />
    </Link>
  );
}

P.S. I put the checks in because the renderer is still called on empty rows after doing a filter (e.g. filtering returns 3 rows but render is called on all visible rows so an icon was rendering on them, at least using server side model with infinite loading)

I also had same problem. I had a columDefs and one of my column has a cellRendererFramework like below(1). In DetailRenderer i was checking if params is null or params.node is group i return null(2). Instead of returning null , i returned empty string and that solved my problem :)
kudos to @DominicTobias

(1)

{
    headerName: "Detail",
    field: "detail",
    cellRendererFramework: DetailRenderer,
  },

(2)

  if (!params || params.node.group || params.value == null) {
    return "";
  }

This fixed my issue for anybody else who may have been getting this. I was returning null for some cell renderers and as a result, ag-grid was throwing an error.

@seanlandsman It may have fixed an issue, however mine was still happening but I realised it's because of the return null - AG thinks the component hasn't rendered. I've change it to this now and it works:

The issue is still reproducible.

More Issues: