You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
logger.error(`Got room state event for unknown room ${event.getRoomId()}!`);
return;
}
This keeps logging error messages. Obviously the event is processed, before the new room is known by the client.
This should be handled more gracefully, because it seams to be a "normal" situation.
And maybe it needs to be changed, so that the needed processing is done, after the room was created?
The text was updated successfully, but these errors were encountered:
We don't use WebRTC, but because of this, we are still impacted:
// NB. We initialise MatrixRTC whether we have call support or not: this is just
// the underlying session management and doesn't use any actual media capabilities
this.matrixRTC = new MatrixRTCSessionManager(this);
This can of course be filtered on our side, but I agree with OP that a more graceful handling from the SDK would be ideal.
@dbkr added new code to MatrixRTCSessionManager in this commit: 6836720
matrix-js-sdk/src/matrixrtc/MatrixRTCSessionManager.ts
Lines 102 to 108 in 95baccf
This keeps logging error messages. Obviously the event is processed, before the new room is known by the client.
This should be handled more gracefully, because it seams to be a "normal" situation.
And maybe it needs to be changed, so that the needed processing is done, after the room was created?
The text was updated successfully, but these errors were encountered: