Unable to sign-in into Android app due to disappearing keyboard

[anlar]

What happened?

Hi,

I'm using Jitsi Android application to connect to Jitsi Meet on self-hosted server.

It works fine if I join as anonymous, but when it is required to sign-in as moderator, to start meeting, I'm unable to use sign-in popup as keyboard disappear when I click on input field.

Android 16, Samsung Galaxy A55.

See attached video:

Screen_Recording_20260204_203721_Jitsi.Meet.mp4

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

v25.6.1 (F-Droid)

Relevant log output

Reproducibility

• The problem is reproducible on meet.jit.si

More details?

No response

[anlar]

Tried v26.0.0 from Play Store - same issue.

[pine919]

Hi @saghul can I work on this issue?

[Calinteodor]

I tried on a simulator that has the same screen dimensions like Samsung A55, but I couldn't repro. Unfortunately, I don't have a Samsung physical device by my side. @pine919 you can propose something, but please, only if you are able to test the fix on a real device. Thank you.

[kapsh]

Same issue in 25.6.1 from fdroid and 26.0 from google play. Login popup activates keyboard, this moves popup up, which closes it and keyboard. Last usable versions available in fdroid are 25.4.0 and 25.5.1 with only minor inconvenience: login popup doesn't move, but because of that keyboard partially hides it.

Device: Samsung A56 running One UI 8.0 based on Android 16.

[anlar]

Actually, problem seems to be with all popup input windows. Below I'm trying to start video share:

Screen_Recording_20260211_205836_Jitsi.Meet.mp4

[Calinteodor]

Ok, I think this is because top and bottom insets are occupying a lot of space and when the native keyboard is visible it forces the modal to fit the small remaining space between those insets.

[Calinteodor]

I linked a PR to this issue. I tested on the devices that I have available and everything looks in order. Can one or some of the reporters test and share a recording from their device to see if the problem is still reproducible? Unfortunately, I don't own Samsung devices and the emulator that replicates one is not very reliable. Much appreciated!

[anlar]

@Calinteodor , not sure if I can build it myself, but if you attach apk built from your branch I can test it on my device.

[Calinteodor]

Can you checkout the fix branch and try cd android && ./gradlew clean && ./gradlew :app:assembleDebug. Should work, unfortunately I cannot attach an apk file here.