Codecov Report

Patch coverage: 43.75% and project coverage change: -0.04% ⚠️

Comparison is base (91ebd58) 90.61% compared to head (981bc66) 90.57%.
Report is 6 commits behind head on dev.

@@            Coverage Diff             @@
##              dev    #7497      +/-   ##
==========================================
- Coverage   90.61%   90.57%   -0.04%     
==========================================
  Files         427      427              
  Lines       15198    15210      +12     
==========================================
+ Hits        13772    13777       +5     
- Misses       1426     1433       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Interesting, I'd also love to know what it is that causes that initial delay. Any hunches? In any case, we'll have to be able to reproduce the problem, otherwise it would certainly be hard to test if the issue is gone after making changes or we'd fully rely on the OP of the bug report.

Any hunches?

I only see one difference currently:
Both methods on initialize create PopoverHolder and set the initial values, both add it to the dictionary, but the the old service is invoking native eventhandler which triggers a non awaitable InvokeAsync(StateHasChanged) while the new service invoking an observable with await InvokeAsync(StateHasChanged).
So my ideas is to try:
A) ask OP to remove the await and try
B) use ConfigureAwait(false) on this method, after this PR was merged (#7441) we do not call any JS on create therefore we don't need to run it on UI synchronization context.

In any case, we'll have to be able to reproduce the problem, otherwise it would certainly be hard to test if the issue is gone after making changes or we'd fully rely on the OP of the bug report

Yeah, that's a big problem. OP says it happens only in their AWS cloud, but i wonder if that happens only on their specific codebase, because I'm sure other BSS folks would report this long time ago.