[Bug]: Login instrumented test on Android fails as element not interactable

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

On Android we run a test using web login.
This since a while fails with:

java.lang.RuntimeException: java.lang.RuntimeException: Error in evaluationEvaluation: status: 12 value: {message=Element is not currently interactable and may not be manipulated} hasMessage: true message: Element is not currently interactable and may not be manipulated
at androidx.test.espresso.web.sugar.Web$WebInteraction$ExceptionPropagator.<init>(Web.java:4)
at androidx.test.espresso.web.sugar.Web$WebInteraction.doEval(Web.java:17)
at androidx.test.espresso.web.sugar.Web$WebInteraction.perform(Web.java:1)
at com.owncloud.android.ui.LoginIT.login(LoginIT.kt:89)

We try to access and enter login name:

// username
        Web.onWebView()
            .withElement(DriverAtoms.findElement(Locator.XPATH, "//input[@id='user']"))
            .perform(DriverAtoms.webKeys(loginName))

Steps to reproduce

1. run LoginIT from Android test suite

Expected behavior

Test should pass

Installation method

None

Nextcloud Server version

master

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

/

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Start with LoginIT.kt at line 89 and inspect the web-login interaction that locates the input with id "user". Run LoginIT from the Android test suite and investigate why the element is not interactable. Done means the login instrumented test passes and can enter the login name successfully.