The error is thrown in the 'useVisualStableUpdate' hook, and looks like this: Error while running updatePages(): Error: Element not part of the array: 'localUserId_camera_TR_VCBysiTy66obcA' not in '[remoteUserId_camera_placeholder, localUserId_screen_share_TR_VSg9wuVhRLLb3B]' or sometimes: Error while running updatePages(): Error: Element not part of the array: 'localUserId_camera_TR_VCBysiTy66obcA' not in '[remoteUserId_pov2_camera_TR_VCdHymFE62sM4w, localUserId_screen_share_TR_VSg9wuVhRLLb3B]'

We'll try to update to the latest version and investigate what we've changed. I'll update here if we resolve the issue or not

This issue was recently resolved by my colleague, who removed this block from ParticipantTile:

const trackReference: TrackReferenceOrPlaceholder = React.useMemo(() => {

return {

participant: trackRef?.participant ?? maybeTrackRef?.participant ?? p,

source: trackRef?.source ?? maybeTrackRef?.source ?? source,

publication: trackRef?.publication ?? maybeTrackRef?.publication ?? publication,

};

}, [maybeTrackRef, p, publication, source, trackRef]);

...and used only:

const trackReference = const trackReference = trackRef || maybeTrackRef

And in FocusLayout, he passed

trackRef={trackRef}

directly as a prop. Apparently the cause was some kind of context mixup. Here is his comment: "This PR removes the TrackRefContextIfNeeded from the ParticipantTile component. ParticipantTile is intended to be used as a child of the TrackLoop component which already adds the TrackRefContext or by passing a track reference as a property." (We now do the latter.) I'm not sure how this bug could exist only for us, since by default those parts are included in the standard components; we've made minimal modifications. But in any case the fix works.