Jump to content

Search the Community

Showing results for tags 'breaking changes'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 1 result

  1. joggs

    Log of breaking changes

    Hi, Do we have a log over breaking changes for each release (dev and prod)? If not, we should. Either in a release log connected to the release in some way or a new post in this forum at the same time as the server update is published. It requires a little bit of extra administration, but the win for the app and plugin developers are bigger in my opinion. I just experienced this scenario: My emby application that communicates with the rest api all of a sudden started to thow exceptions. After some searching I see that the serialization of the json responses to the automatically generated entity classes, based on the json response, was broken. This means that something has changed in the json response that I receive from the server, and this time in the usersession response object. After regenerating the usersession entity class, everything works again. I rather read about all breaking changes for a release instead of testing all features in my application and see if anything breaks. Again, I know you have a lot to do, so it is undestandable if you don't want to add more things to the admin part of a release. Keep up the good work! Joggs
  • Create New...