Administration of Library unaccessible

[fox1986 11]

All of a sudden, I cant administrate my library with the Android app anymore. Every time I click on the folders I received an error message (see below) that I have to use the Web interface instead which I quite inconvenient.

This happened in the Beta and Non Beta (3.5.12) version as well. Running Envy Server 4.8.11 in Synology Nas. Reinstalling the app and cleaning cache didn't solve the problem.

[Luke 42077]

Hi, you’ll need to either use the web app or update to Emby server 4.9

[fox1986 11]

Might be helpful to add this information to the error message. I wasn't aware that I am forced to update the server to keep access to the administration via app.

However I guess I will wait with the update anyway, I am a little worried about the recent reports that my meta files get messed up after updating as stated in another topic.

[Gilgamesh_48 1240]

4 hours ago, fox1986 said:

Might be helpful to add this information to the error message. I wasn't aware that I am forced to update the server to keep access to the administration via app.

However I guess I will wait with the update anyway, I am a little worried about the recent reports that my meta files get messed up after updating as stated in another topic.

I update to every release pretty much as soon as it is available and nothing has ever messed up my metadata. I did have one that kind of screwed up some images but as soon as that was fixed and Emby made a new update everything was fine. 

I know that paranoia is rampant across the internet, and some of it is true, but failing to update because a very few people had some problems seems kind of like the old saying, "Throwing out the baby with the bath water."

I have only once, many years ago, had an Emby upgrade screw up my metadata and even then a rescan of my library fixed it after Emby fixed the bug that caused the problem.

I delay just a little on every upgrade but I install it within 6-8 hours after it shows up. 

I do not understand delaying much beyond that as I like to run with the best code possible.

BTW: It sounds to me like the metadata problems many people report are more self inflicted that bugs in the code.

Edited October 18, 2025 by Gilgamesh_48

[Luke 42077]

5 hours ago, fox1986 said:

Might be helpful to add this information to the error message. I wasn't aware that I am forced to update the server to keep access to the administration via app.

However I guess I will wait with the update anyway, I am a little worried about the recent reports that my meta files get messed up after updating as stated in another topic.

Hi, yes we will add that to the message. Thanks.

[fox1986 11]

9 hours ago, Gilgamesh_48 said:

I update to every release pretty much as soon as it is available and nothing has ever messed up my metadata. I did have one that kind of screwed up some images but as soon as that was fixed and Emby made a new update everything was fine. 

I know that paranoia is rampant across the internet, and some of it is true, but failing to update because a very few people had some problems seems kind of like the old saying, "Throwing out the baby with the bath water."

I have only once, many years ago, had an Emby upgrade screw up my metadata and even then a rescan of my library fixed it after Emby fixed the bug that caused the problem.

I delay just a little on every upgrade but I install it within 6-8 hours after it shows up. 

I do not understand delaying much beyond that as I like to run with the best code possible.

BTW: It sounds to me like the metadata problems many people report are more self inflicted that bugs in the code.

Sorry but not blindly trusting and installing every update as soon as it comes out, especially when other report serious problems with that update isn't "paranoia". It's a huge risk (there is good reason why in many companies, you first need clearance for an update by your IT, as a faulty update can make you inoperable or ruin weeks of work) nowadays

 

However. I made a backup and tried the update. So far my metadata looks fine.