Recording option in jitsi meet mobile view

[Harshavardhan77300]

What happened?

In jitsi meet, recording option is not visible for mobile view. How can i enable the recording option

Platform

• Chrome (or Chromium based)
• Firefox
• Safari
• Other desktop browser
• Android browser
• iOS browser
• Electron app
• Android mobile app
• iOS mobile app
• Custom app using a mobile SDK

Browser / app / sdk version

jitsi-meet-2.0.9909-1, jitsi-meet-prosody-1.0.8302-1,

Relevant log output

No response

Reproducibility

• The problem is reproducible on meet.jit.si

More details?

No response

[saghul]

Did you deploy Jibri? It it functional on the web version?

[Harshavardhan77300]

yes jibri also deployed

[saghul]

Does it work in the desktop web version? Note that local recordings are not using Jibri so while you may see that it's not an indication of recordings working.

[Harshavardhan77300]

Yes in desktop Web version it is working, but in mobile view even recording icon also not displayed.

[saghul]

Can you share a screenshot of what you see on the desktop web?

[Harshavardhan77300]

[Harshavardhan77300]

even in 3dots (more icon) also there is no recording button
but in desktop is was displaying

[saghul]

That's not our UI though. Does the vanilla UI work?

[Harshavardhan77300]

now i got that recording icon but it was not starting getting error
UnhandledPromiseRejection: [object Element] StackTrace: undefined
no Jibris available

bu the jibri server is in active only

[damencho]

Check jibri logs.

[Harshavardhan77300]

[damencho]

Hard to figure out from a screenshot snippet whether it connected to the control room.

[Harshavardhan77300]

then could please tell what i need to share now?

[damencho]

The whole file.

[Harshavardhan77300]

GNU nano 7.2 /var/log/jitsi/jibri/log.0.txt
2025-01-13 17:39:38.398 INFO: [1] MainKt.handleCommandLineArgs#188: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2025-01-13 17:39:38.511 INFO: [1] MainKt.setupLegacyConfig#213: Checking legacy config file /etc/jitsi/jibri/config.json
2025-01-13 17:39:39.075 SEVERE: [1] JibriConfigKt.loadConfigFromFile#198: A required config parameter was missing: Instantiation of [simple type, class org.jitsi.jibr>
2025-01-13 17:39:39.076 INFO: [1] MainKt.setupLegacyConfig#221: Parsing legacy config file failed
2025-01-13 17:39:39.101 INFO: [1] MainKt.main#55: Jibri starting up with id
2025-01-13 17:39:39.111 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_started' was renamed to 'sessions_started_total' to ensure consistent metric>
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'sessions_stopped' was renamed to 'sessions_stopped_total' to ensure consistent metric>
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'errors' was renamed to 'errors_total' to ensure consistent metric naming.
2025-01-13 17:39:39.117 FINE: [1] MetricsContainer.registerCounter#152: Counter 'busy' was renamed to 'busy_total' to ensure consistent metric naming.
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_connected' was renamed to 'xmpp_connected_total' to ensure consistent metric nam>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnecting' was renamed to 'xmpp_reconnecting_total' to ensure consistent metr>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_reconnection_failed' was renamed to 'xmpp_reconnection_failed_total' to ensure c>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_ping_failed' was renamed to 'xmpp_ping_failed_total' to ensure consistent metric>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed' was renamed to 'xmpp_closed_total' to ensure consistent metric naming.
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'xmpp_closed_on_error' was renamed to 'xmpp_closed_on_error_total' to ensure consisten>
2025-01-13 17:39:39.118 FINE: [1] MetricsContainer.registerCounter#152: Counter 'stopped_on_xmpp_closed' was renamed to 'stopped_on_xmpp_closed_total' to ensure consi>
2025-01-13 17:39:39.446 INFO: [1] JwtInfo$Companion.fromConfig#176: got jwtConfig: {}

2025-01-13 17:39:39.446 INFO: [1] JwtInfo$Companion.fromConfig#186: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/>
2025-01-13 17:39:39.453 FINE: [1] RefreshingProperty.getValue#46: Refreshing property jwt (not yet initialized or expired)...
2025-01-13 17:39:39.500 INFO: [1] MainKt.main#128: Using port 3333 for internal HTTP API
2025-01-13 17:39:39.529 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:39:39.858 INFO: [1] XmppApi.updatePresence#203: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, >
2025-01-13 17:39:39.866 INFO: [1] MainKt.main#154: Using port 2222 for HTTP API
2025-01-13 17:40:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:41:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:42:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:43:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:44:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:45:39.466 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:46:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2025-01-13 17:47:39.465 FINE: [27] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status