Nam Le

> This feels like whack-a-mole. Isn't the root problem that you've got IModelApp inside some React state that's repeatedly getting recreated? You're right that it is whack-a-mole, but we can't...

it would be great to do this yes, we would have to do some experimenting in context of `rush`, see how to invoke sharding there and if it messes up...

Closing this, parsing bearing with lowercase letters was introduced in https://github.com/iTwin/platform-bentley-community/issues/121 Based on this [comment](https://github.com/iTwin/itwinjs-core/issues/7487#issuecomment-2566543805) in another issue, it seems like AccuDraw's input fields would ignore the error our parsing...

If you open the network tab in the dev tools, are there any requests that fail in 4.7 that wasn't in 4.6?

Is the simple example from `npx create-react-app` also using 4.7 packages? And that is loading the model correctly?

I can't see CSS being the cause... if the tree on the side is shown, and you're able to see some stuff rendered on the page, and within the viewport......

It's not too clear what the root cause is yet... I see from your package.json that you jumped straight to 4.7.5. Could you downgrade that to `4.7.0`? Let's see if...

In the network tab, can you filter for these following requests that start with `api.bentley.com/imodel/rpc/v4`? If any are failing, please provide the x-correlation-id header value of those errors, so we...

if you were to compare the network requests and the waterfall between the sample viewer and your implementation of the viewer, are there discrepancies in the flow? Maybe some requests...

I'm curious, maybe the redundant requests are coming from a mismanagement of react lifecycle? Maybe the inititalization is being triggered twice (although it might be running twice because of react's...