Dev had it fixed in 1.28.3 how did this fix not get merged before 1.29? Why did it push out as a beta of an entirely new version for linux? It’s fantastic that you’re introducing new features for windows but can you not actively break linux in the process?
I can’t even download 1.28.3 anymore to go back since the link is dead.
Sounds like something Plex can help get sorted.
In the meantime, you can roll back a couple of ways, usually 
As I explained earlier,
A developer’s in-process, experimental, build had been given.
As pure matter-of-chance, it was based on version 1.28.3 but had a newer build number (the last 4 digits).
That build is not in the qa-production release queue and that work, having not passed QA, would not be in 1.29.0.
Experimental builds are just that – experimental.
The files may last a few hours or a few minutes; all at the developer’s discretion.
I have forwarded the request to grant access again.
This is not “breaking linux”. Advanced access was given by the developer.
The file was then apparently deleted by the user.
Closing this thread as this has been explained elsewhere.
