[AnalyticalTable > Subcomponents]: VirtualTableBody tries to update AnalyticalTable during its render

[Greggics]

Describe the bug

On AnalyticalTable components with the renderRowSubComponent prop set, and the subComponentsBehavior prop set to "IncludeHeightExpandable" I get the following error message when I collapse a table row for the first time:

Cannot update a component (`AnalyticalTable`) while rendering a different component (`VirtualTableBody`). To locate the bad setState() call inside `VirtualTableBody`, follow the stack trace as described in https://react.dev/link/setstate-in-render

Note: This only happens the very first time you collapse a row since the last page load. Not even unmounting and remounting seems to trigger this error again. You have to refresh the page for the this error to occur again.

I also tried it with multiple AnalyticalTable components. The error seems to trigger the first time any of the tables rows is getting collapsed. It won't trigger on the other table anymore at that point.

Isolated Example

https://stackblitz.com/edit/github-ccdfvjhn?file=src%2FApp.tsx

Reproduction steps

1. Open the example
2. Open the Browser Development Tools
3. Expand any of the rows
4. Collapse a row of your choice
5. Get error message in the console saying "Cannot update a component (AnalyticalTable) while rendering a different component (VirtualTableBody). To locate the bad setState() call inside VirtualTableBody, follow the stack trace as described in https://react.dev/link/setstate-in-render"
6. The error will not occur anymore. Refresh the page and start again from (3.) to re-trigger the error.

Expected Behaviour

No response

Screenshots or Videos

No response

UI5 Web Components for React Version

2.5.0

UI5 Web Components Version

2.5.0

Browser

Chrome, Edge, Firefox

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[Logudaf]

Hello,
Is there any temporary fix for this issue?
Thank you.

[pop1989bb]

@Lukas742 Do you have an idea when this issue will be researched?

[Lukas742]

Hi all,

while the error is of course unintended, it doesn’t appear to break the implementation, which is why we initially treated this issue with low priority. However, if the component or application is crashing for you, or if you're experiencing any other unexpected behavior, please let us know.

That said, I’ll try to prioritize the issue more. I’ve already taken a quick look at the root cause last week, but unfortunately, it doesn’t seem easy to resolve and will likely require significant refactoring effort.

[ui5-webcomponents-react-bot]

🎉 This issue has been resolved in version v2.11.0 🎉

The release is available on v2.11.0

Your semantic-release bot 📦🚀

[pop1989bb]

Thank you @Lukas742