Kick out a member

Today I cannot kick out a member by Jitsi on my browser …only frm the smarthphone


Thank you for the report!
I confirm this is broken at the moment on We will work on fixing it.

Many thanks for your reply.

I hope you may work on it … soon … it’s very useful this option …
and his absence is missing.
I hope that very soon you can restore the functionality …please please

It is fixed, we need to update with it … Will bring it to the team tomorrow and will try to do it soon

Many thanks for your work and reply !!!

It is fixed now on

Many many thanks for your message.
I am very grateful to you for your quick work!

But I still received TypeError on the Kick button click.

Logger.js:154 2020-11-18T04:03:26.135Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Script error. Script:  Line: 0 Column: 0 StackTrace:  null
o @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:613
window.onerror @ middleware.js:110
Logger.js:154 2020-11-18T04:03:26.135Z [modules/statistics/CallStats.js] <Function._reportError>:  No error is passed!
o @ Logger.js:154
_reportError @ CallStats.js:198
sendApplicationLog @ CallStats.js:447
b.sendLog @ statistics.js:732
b.reportGlobalError @ statistics.js:768
getGlobalOnErrorHandler @ JitsiMeetJS.js:619
window.onerror @ middleware.js:110

AbstractKickButton.js:44 Uncaught TypeError: e is not a function
    at Object._handleClick (AbstractKickButton.js:44)
    at Object.f (react-dom.production.min.js:15)
    at _ (react-dom.production.min.js:15)
    at react-dom.production.min.js:16
    at j (react-dom.production.min.js:16)
    at A (react-dom.production.min.js:17)
    at C (react-dom.production.min.js:17)
    at D (react-dom.production.min.js:17)
    at Mn (react-dom.production.min.js:85)
    at Rn (react-dom.production.min.js:87)
    at t.unstable_runWithPriority (scheduler.production.min.js:20)
    at pa (react-dom.production.min.js:113)
    at bs (react-dom.production.min.js:207)
    at zn (react-dom.production.min.js:86)

@SushantGautam is this on

Do you repro it now?

Yes still. On

@SushantGautam when you reproduce can you open the javascript developer console in the browser and tell me the value of config.deploymentInfo.shard, thanks.

Ups, found it and fixed it, there were two shards in ap region with the wrong version for the client code.

Yes sir! It’s fixed now.
I was having trouble with my self-hosted instance with prosody 0.10. Is there a patch for the kick feature for that version?

At one of the clusters, I tried to upgrade to 0.11+. And applied the patch. The kick feature worked then.
But no options/patch found for prosody 0.10.

No idea about 0.10. There is a known issue we have seen with ghost participants with 0.10. So you better use 0.11.

1 Like