“Configure monorepo” page crashes to blank page, React/Next.js error: Maximum update depth exceeded

I’m trying to add a new service to an existing monorepo in SonarCloud, but the “Configure monorepo” page does not load correctly.

Instead, it keeps loading for a while (the address bar changes rapidly multiple times) and then crashes to a blank page. I reproduced this across multiple browsers and laptops, so it seems unrelated to my local setup.

In the browser console I see this error when I click the reactjs detailed error:

Maximum update depth exceeded

So it looks like the page may be hitting a frontend render/update loop.

I’ve attached a screenshot. Is this a known issue, or is there anything I can do to work around it?

Hi,

We’ve tried but can’t reproduce this. We think it’s related to your context. Can you share your Org ID?

 
Thx,
Ann

1 Like

Hi @ganncamp , sure that is ‘enablenow’. It still fails when trying to configure our monorepo to add a service.

We have the same issue (org key vitalthings)

Hi,

We have the same issue in our GitHub organization kwatera-project for repository KWATERA.

When trying to configure the monorepo / add another service, the page keeps bouncing between /projects/create and /projects/create?search=KWATERA, then ends on a blank white screen.

I reproduced it multiple times, including after waiting overnight, in incognito mode, and in another browser, so it does not look like a local cache/browser issue.

Hi all,

Welcome to the community and thanks for these reports, @torb and @lukasz2! (Thanks for your report too @rodyvansambeek. :smiley:)

We’ve opened an incident for this and are working on a fix.

In the meantime, can you try this workaround: Instead of clicking on the “Configure monorepo” link (displayed on “repository A”, let’s say), click on “Setup a monorepo.” on the right of the “Analyze new project” page and then select the “repository A” in the list of repositories. That should bypass the problem.

 
HTH,
Ann

Thank you. That workaround did the trick for me :+1:

1 Like

Thanks. Confirmed, this workaround solved the issue on our side too.

Hi all,

The fix has been deployed. No need to use the workaround anymore if you don’t want to. Sorry for the trouble.

 
Ann