Order of life cycle method calls with error boundaries is unexpected

I have a requirement for my app to track when a component has completed rendering and whether the render ended in success or failure. I expected to be able to use the componentDidMount/componentDidUpdate life cycle methods along with an error boundary's componentDidCatch method to handle both success and failure cases.

However, I am noticing that the order of the life cycle methods is not what I expect. When an exception is raised within a child component in the error boundary, the component's componentDidMount/componentDidUpdate method will get called first before componentDidCatch. So I can't simply use componentDidMount/componentDidUpdate to determine that my scenario ended in success.

Is this a bug? How would I go about achieving this scenario?

未指定檔案、測試或進入點。先找出涵蓋 componentDidMount、componentDidUpdate、componentDidCatch 和錯誤邊界的 React 文件，然後驗證所回報的生命週期順序。當預期行為以及一種受支援的區分渲染成功與失敗的方法都清楚記錄後，即表示完成。