Publish a new release?
Hey, I made an account to ask you, why are there no new release tags?
The release on F-Droid, as well as on your Website, are very old, at least for Android standards.
I saw that you are very active with commits, but I have no idea how F-Droid makes releases.
Choosing a random git commit is not a nice experience.
Even if it is just a point release, is making a release tag possible? That would be great.
Activity
Hi,
We are having issues with the Play Store due to some of their policy updates, and haven't yet found a compromise that works.
The short version is that we can't release on Android TV anymore without either giving Google our private signing key, or we have to drop support for TV under API 30 / Android 11, which is most of our TV users.
For the longer / more technical version, you can checkout https://dev.to/npomepuy/vlc-for-android-updates-on-the-play-store-179j it's a blog post that VLC-Android's lead dev wrote to explain the situation.
We are sorry for the inconvenience, we have been stuck with this for the past few months, and it is also frustrating for us.
F-Droid makes their own releases builds based on our release tags, but if we did a special release tag for them, that would mean bypassing the beta process that we go through with the Play Store, and subjecting F-Droid users that did not sign to be beta testers to all the issues that would come with it.
In the mean time if you want to get the latest features, we do publish vlc-android builds every night based on the current master with an auto-update that we added recently so you can have regular updates if you wish without having to download another apk. You can find them at https://artifacts.videolan.org/vlc-android/nightly-arm64/.
Edited by Duncan McNamaraThank you for the response.
The problem is that the website uses https://get.videolan.org/vlc-android/3.5.4/ As source, latest version on get is 3.5.4
There are a lot of different versions, The one on website, which is on https://get.videolan.org/vlc-android And needs to be updated manually. There is also https://get.videolan.org/testing/android/ which used to be used for betas.
However, now it seems that main source is artifacts, which also have different versions:
- https://artifacts.videolan.org/vlc-android/nightly-arm64/
- https://artifacts.videolan.org/vlc-android/release/
But, these cant be installed, as they use different signatures apparently,
Has the team decided which source will be used for official app, so that users can update app with uninstalling and reinstalling each time?
-
https://get.videolan.org/vlc-android/3.5.4/ is the official source for the 3.5.4 release.
In general, get.videolan.org is the official release source for any videolan project.
https://artifacts.videolan.org/vlc-android/release/ is where Gitlab puts the release once it's been built by the CI. This is not yet signed as a release, and you should not use this. It's mostly for our internal release process, the apk is signed manually on our side before being reuploaded to the store and get.videolan.org.
https://artifacts.videolan.org/vlc-android/nightly-arm64/ is where Gitlab puts nightly builds. These are not release builds but nightly debug builds, and if you install an apk from there, it will not replace your vlc installation, but install a second "debug" vlc with a different background color for the icon like this:
These builds are built every night on master, and are mostly used when exchanging about issue with users, to see if an issue was fixed, or some users want to have an up to date build.
Sorry, the response above wasn't clear about the type of build nightlies were.
mentioned in merge request !1992 (merged)
