element-call icon indicating copy to clipboard operation
element-call copied to clipboard

Unable to properly hangup from call

Open baconsalad opened this issue 9 months ago • 4 comments

Steps to reproduce

  1. Join private server.
  2. Join call.
  3. Hangup.

Outcome

What did you expect?

Hangup.

What happened instead?

It fails to hangup. You are still on the call, can hear and see everyone but it appears to everyone that you left. This happens for all participants.

I grabbed this from console after clicking the red hangup button. (ignore the poor layout)

rageshake.ts:500 Failed to send hangup action tw: Unknown or unsupported action: im.vector.hangup
    at Koe.handleResponse (https://skittles/assets/index-52Ns62Lx.js:34:58588)
    at Koe.handleMessage (https://skittles/assets/index-52Ns62Lx.js:34:58153)
    at https://skittles/assets/index-52Ns62Lx.js:34:57833

window.console.<computed>	@	rageshake.ts:500
(anonymous)			@	rageshake.ts:639
GHe				@	rtcSessionHelpers.ts:162
await in GHe		
LU				@	rtcSessionHelpers.ts:182
await in LU		
(anonymous)			@	GroupCallView.tsx:327
onClick				@	InCallView.tsx:588

MatrixRTCSession Not joined to session in room !ABC:url: ignoring leave call

Operating system

All

Browser information

Several

URL for webapp

no

Will you send logs?

No

baconsalad avatar Mar 28 '25 18:03 baconsalad

can you please provide logs or rage-shakes. We cannot repo on our end.

fkwp avatar Mar 31 '25 15:03 fkwp

No, but I'll do some digging on my end when I get the chance.

baconsalad avatar Mar 31 '25 19:03 baconsalad

Other stuff spergs out when you initially join. I don't have encryption set up for that room and can't remember the reason why as I set this all up a while ago. May be relevant.

rageshake.ts:500 Failed to set E2EE enabled on room Error: e2ee not configured, please set e2ee settings within the room options
    at Ac.<anonymous> (livekit-client.esm.mjs:22658:6)
    at Generator.next (<anonymous>)
    at livekit-client.esm.mjs:6677:1
    at new Promise (<anonymous>)
    at J (livekit-client.esm.mjs:6672:41)
    at Ac.setE2EEEnabled (livekit-client.esm.mjs:22651:15)
    at useLiveKit.ts:119:6
    at Object.useMemo (react-dom.production.min.js:179:191)
    at Dne.yt.useMemo (react.production.min.js:26:48)
    at DUe (useLiveKit.ts:117:22)
window.console.<computed>	@	rageshake.ts:500

rageshake.ts:500 Failed to send join action JS: Unknown or unsupported action: io.element.join
    at koe.handleResponse (https://URL/assets/index-M_QdIP0W.js:34:58588)
    at koe.handleMessage (https://URL/assets/index-M_QdIP0W.js:34:58153)
    at https://URL/assets/index-M_QdIP0W.js:34:57833
window.console.<computed>	@	rageshake.ts:500

rageshake.ts:500 Failed to send layout change to widget API JS: Unknown or unsupported action: io.element.tile_layout
    at koe.handleResponse (https://URL/assets/index-M_QdIP0W.js:34:58588)
    at koe.handleMessage (https://URL/assets/index-M_QdIP0W.js:34:58153)
    at https://URL/assets/index-M_QdIP0W.js:34:57833
window.console.<computed>	@	rageshake.ts:500
(anonymous)	@	rageshake.ts:639
(anonymous)	@	InCallView.tsx:359
Promise.catch		
(anonymous)	@	InCallView.tsx:358

baconsalad avatar Apr 01 '25 01:04 baconsalad

I get "Error leaving RTC session"

532910 avatar Sep 17 '25 20:09 532910