[lib-jitsi-meet] [jibri] Problem with Jibri and our custom UI implementation

Giamme · October 7, 2020, 2:03pm

Hello everyone,

We are trying to use Jibri with our custom front-end developed using “lib-jitsi-meet”.

When using Jibri to record the conference and store the recording on our server we get this errors:

org.jitsi.jibri.selenium.pageobjects.CallPage.apply() Not joined yet: APP is not defined
org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Timed out waiting for call page to load

It seems like the error gets fired inside this class here:

github.com

jitsi/jibri/blob/6dc6de254a9813a9e1e12fb6db224d57a3ce3e91/src/main/kotlin/org/jitsi/jibri/selenium/pageobjects/CallPage.kt#L48


}

override fun visit(url: String): Boolean {
    logger.debug("Visiting url $url")
    if (!super.visit(url)) {
        return false
    }
    val start = System.currentTimeMillis()
    return try {
        WebDriverWait(driver, 30).until {
            val result = driver.executeScript("""
                try {
                    return APP.conference._room.isJoined();
                } catch (e) {
                    return e.message;
                }
                """.trimMargin()
            )
            when (result) {
                is Boolean -> result
                else -> {

We came to the conclusion that our front-end is missing an APP object(“Not joined yet: APP is not defined”).

By checking on the actual “jitsi-meet” code we learned that you are creating an APP object inside window, we tried to do something similar by putting our conference object inside APP like you are doing in your source code but it doesn’t seem to resolve the issue, we actually get the same errors.

How can we set our front-end to give Jibri what it needs to do its things?

George_Dwomoh · October 29, 2020, 11:00am

I dont think that is possible with jibri out of the box. You should probably try modifying jibris code youself

bbaldino · October 29, 2020, 4:30pm

If that is accessible (APP.conference._room.isJoined()), then it should work. I’d look again at how you’re exposing APP and see if you can access that from the console…Jibri isn’t doing anything special there.

Giamme · November 4, 2020, 9:47am

Thanks @bbaldino
That’s exactly how we solved it.

We just had to expose the isJoined function from JitsiConference inside this path window.conference._room