Android App silently "crashes" when switching networks

[brothom 219]

I'm experiencing issues when I'm using the Android App and from move the same location as the server to the cell/mobile network.
Reproduction is fairly simple, especailly when using Music.

Reproduction

1. Open the Android App and connect to a server on the same local network
MUST be on the same network
2. Open a playlist / songs and press play
3. Disconnect WiFi or move outside the range of your wifi
4. The App will continue to play as a long as buffered, but when it tries to buffer it infinitely loads

What should fix it, but doesn't

The app becomes unresponsive. Browsing seems to work to some degree but playing any other piece of media won't.
What doesn't seem to fix the issue:

* Stopping the playlist and start something else doesn't fix playback
* Closing and reopening the app doesn't fix playback

The only thing that seems to work is just to close the app and wait for 5 to 10 minutes and reopen it after.

Potential cause

The cause of this issue seems to be that all Emby apps/platforms seem to connect to the local IP-address when connecting from the same network as the server. This causes issues when playback is underway and the network is switched.

This also causes issues when the app is already launched and the network is switched, since the app seems to want to connect to the local IP-address.

Edited May 11 by brothom

[Luke 42528]

Hi, what version number of the app are you running?

[brothom 219]

4 hours ago, Luke said:

Hi, what version number of the app are you running?

I think it's 3.5.32? I have to say that this issue also occurs within the browser but "refreshing" it fixes the issue sometimes whilst that is not possible within the app. 

I still have a gut feeling it's trying to connect to the local ip-address instead of the domain (if available). 

Using Emby through wifi, traffic goes through 192.168.x.x
Using Emby from net/outside of the network, traffic goes through whatever.xyz

Shuffling between these networks just causes the local ip to always become unavailable. Wouldn't it be more sensible to "always" use the domain if it's set and otherwise maybe attempt to remember both remote and local ip-addresses if no domain is available?

Edited May 20 by brothom