jelly vers androidtv

[jellynoob1994]

morning


did some one forget to push the latest jellfin version to the playstore ??

[niels]

Can confirm I did not forget any steps in the currently ongoing publishing process 😉. The new release is currently available for 5% of users on Both GPlay and Amazon.

[jellynoob1994]

so it wasnt me tripping....

playstore being playstore gotcha

[engmaxneto]

Hi, just to update,

Still not in the google store and the apk won´t upgrade in neither android tv nor google cromecat tv

Best regards

[jellynoob1994]

no worries my experience with the playstore is the same sometimes an update will go trough in days sometimes weeks its just a waiting game praying to the playstore gods...

[jellynoob1994]

Hi, just to update,

Still not in the google store and the apk won´t upgrade in neither android tv nor google cromecat tv

Best regards

also you can update your TV by hand with a flash drive the most actual apk. can be found on the android tv github i believe its 0.18.3 atm

[TheDreadPirate]

The roll out had been increased to 20% of users, the last time I checked in with Niels. So still not fully rolling out yet.

[niels]

I got sick last week which delayed everything a bit, as I was unable to work on bug reports (and we had some significant bugs that needed fixing!). I'm back now and the rollout is currently at 50% for both Amazon and Google users, this means that roughly half of all users will get the update right now. Unless any issues arise this will be increased to 100% near the end of this week.

[LadyZero]

@niels I think it would be beneficial and interesting for the community to understand what happens after you push an update to the app stores.

After you push an update to the app stores, several processes typically occur:

    Submission Review: The app store (like Apple's App Store or Google Play) will review the update to ensure it complies with their guidelines and policies. This can take anywhere from a few hours to several days, depending on the store and the complexity of the update.

    Testing: The app store may run automated tests to check for crashes, performance issues, and compliance with technical requirements. They may also conduct manual testing for certain types of updates.

    Approval or Rejection: If the update passes the review, it will be approved and made available to users. If there are issues, the update may be rejected, and you will receive feedback on what needs to be fixed.

    Release: Once approved, the update is published to the app store. Users will be notified of the new version, and it will be available for download or automatic updates, depending on their settings.

Some users receive updates first due to a staged rollout strategy, where developers gradually release the update to a small percentage of users to monitor for issues before a wider release. This approach helps identify potential bugs or performance problems in a controlled environment, allowing developers to address any issues before the update reaches all users.

Would you say this is correct?

[niels]

I did explain the process somewhere a few weeks ago but I can't remember where and am unable to find that now 😅. What you said is mostly how it works yes. Once the release is visible on GitHub we start the publishing part which often takes a few days for the stores to approve and then me gradually increasing rollout and watching for any major issues. Most patch releases (where only the last digit changes) get a full rollout, 0.18.3 was a "special" one that I explicitly postponed until after new year so no new major issues would arise for people using Jellyfin during their new years festivities.