After losing connection to server, client returns to server address input screen

[davidrutland]

Describe the bug

This affects version 2.3.2 onwards on Android- so I've downgraded to 2.3.1

Be playing audiobooks while driving.
Connection drops.
Audiobook continues, but Jellyfin returns to server address input screen (as if the server had moved rather than the more obvious explanation)
Hit 'Connect'
Audiobook continues continuing, but controls (play/pause/currently playing) is gone
Eventually, audiobook stops.

Up to and including 2.3.1 this did not happen. Connection dropped and Jellyfin just stayed on the same screen. Still able to pause / resume etc. Shortish interruptions did not affect playback at all.

Logs

No - because I downgraded.

Application version

2.3.2 upwards

Where did you install the app from?

F-Droid

Device information

Sony G8341

Android version

Android 9

Jellyfin server version

10.7.7.0

Which video player implementations does this bug apply to?

• Web player (default)
• Integrated player (ExoPlayer)
• External player (VLC, mpv, MX Player)

[Sarlay]

I have the same issue

[comfreak89]

I have a similar issue on 2 devices: we loose the connection when playing trailers.

[exalented]

This issue can be resolved by setting the PublishedServerUrl. Seeing as though removing this fixed DLNA problems in the past it's resonable that people would be encountering this issue. Note that jellyfin-android would not successfully connect without a trailing / in the client (this is also the case with the WebOS client). This has been tested and seems to work with 'multi-domain' where you can access it both publically and on your lan, with and without https.

Configure your server something similar to this and reverse proxy if you need.

    environment:
      - JELLYFIN_PublishedServerUrl=http://server:8096/media

[SegiH]

If anyone wants to delve into the source code, I found the place where this is being triggered: java/org/jellyfin/mobile/fragment/ConnectFragment.kt in override fun onViewCreated which is defined as:

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)

        // Apply window insets
        ViewCompat.requestApplyInsets(serverSetupLayout)

        hostInput.setText(mainViewModel.serverState.value.server?.hostname)
        hostInput.setSelection(hostInput.length())
        hostInput.setOnEditorActionListener { _, action, event ->
            when {
                action == EditorInfo.IME_ACTION_DONE || event.keyCode == KeyEvent.KEYCODE_ENTER -> {
                    connect()
                    true
                }
                else -> false
            }
        }
        connectButton.setOnClickListener {
            connect()
        }
        chooseServerButton.setOnClickListener {
            chooseServer()
        }

        if (arguments?.getBoolean(Constants.FRAGMENT_CONNECT_EXTRA_ERROR) == true)
            showConnectionError()

        // Show keyboard
        serverSetupLayout.doOnNextLayout {
            @Suppress("MagicNumber")
            hostInput.postDelayed(25) {
                hostInput.requestFocus()

                requireContext().getSystemService<InputMethodManager>()?.showSoftInput(hostInput, InputMethodManager.SHOW_IMPLICIT)
            }
        }

        discoverServers()
    }

The 2 lines above:

        if (arguments?.getBoolean(Constants.FRAGMENT_CONNECT_EXTRA_ERROR) == true)
            showConnectionError()

are being triggered which sends the user back to the server address input screen. I tested this out in Android Studio by running the Android client in the emulator, logging into my instance of JF and then enabling airplane mode in the emulator to replicate this behavior.

[SegiH]

ith the WebOS client)

exalented,

Are you supposed to use the local or public URL for the value of this var ? I used the local URL because I'm behind a reverse proxy but still have this issue

[exalented]

I run 10.8.0_alpha3 behind two reverse proxies actually.

JELLYFIN_PublishedServerUrl is a local address within my LAN. When you connect to your instance make sure you have a trailing slash (/). So for example you'd goto the following in a browser, the WebOS wrapper or the android client:
http://jellyfinserver.local:8096/media/ or https://jellyfinserver.tld/media/ .

[SegiH]

Thanks.

I have added the trailing slash which was missing. I will update you with the results

[nielsvanvelzen]

A trailing slash should not matter as the server address normalization code from our SDK takes care of that. If it does change behavior of the app it's a bug.

[jellyfin-bot]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

[SegiH]

I am using Jellyfin for Android 2.4.4 from Play Store on Android 12 and still have this issue with the app when it thinks I've lost my network connection.

[SegiH]

I am still getting kicked back to the "Connect to Server" screen.

I downloaded the Kotlin source for the Android app today and ran it in debugging mode with a breakpoint at

jellyfin-android/app/src/main/java/org/jellyfin/mobile/setup/ConnectFragment.kt

Line 30 in ad4103d

super.onViewCreated(view, savedInstanceState)

This is the same method that I referenced in my previous post but the app was written in Java then and has since been re-written in Kotlin.

I started playing a song while debugging the app and toggled airplane mode to simulate momentarily losing network connection and sure enough, the breakpoint gets hit.

Now in same cases, my connection will go from 5G -> Wifi or 5G-> 4G but the result is the same.