Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: A developer-signed, non-debuggable variant of Termux on GitHub Releases #4094

Open
FixItKit opened this issue Aug 11, 2024 · 5 comments

Comments

@FixItKit
Copy link

FixItKit commented Aug 11, 2024

Feature description

There should be a developer-signed, non-debuggable variant of Termux published on GitHub Releases. GitHub Releases is the fastest way to get new updates since you don't have to go through Google Play's or F-Droid's update review processes. You can keep the Termux app up-to-date by manually checking for updates or using an app to automatically check for updates/update it for you.

Additional information

Most Android developers using GitHub Releases publish developer-signed, non-debuggable apps.

@FixItKit FixItKit changed the title [Feature]: A developer-signed, non-debuggable variant of Termux on GitHub Releases. Aug 11, 2024
@sylirre
Copy link
Member

sylirre commented Aug 19, 2024

Agree, but here's an issue: current situation would require introducing a new signature key as current maintainers don't have access to one used for Google Play. F-Droid uses its own either.

3 different signatures already confuse users (testkey, Google Play, F-Droid). Adding the fourth one would make it even worse.

@agnostic-apollo
Copy link
Member

There are plans to publish another source on our site after/with next main release, a key was already generated. Publishing both debug and release builds on github would be problematic, there are already separate android 5/6 and 7+ variants and users have been blindly downloading the android 5/6 variants, as its download count is much higher than the android 7+ ones, which it should not be, will fix that in next beta. We may eventually need to release different execution type/targetsdk variants too.

Playstore having removed sharedUserId without warning users if a plugin is installed from a different source has already created a mess, as signatures don't need to be same for main termux app and plugins.

So ultimately situation would get worse if another key is added, even though we may need to.

@FixItKit
Copy link
Author

FixItKit commented Aug 19, 2024

Maybe offer a short explanation on which APK to pick or add a link to some webpage explaining releases for those who don't know already.

@agnostic-apollo
Copy link
Member

Yeah, I already have written docs for it, but they aren't complete yet due to some blockers.

@agnostic-apollo
Copy link
Member

I have manually added a downloads section to the release info, that should help. On mobile site, github does not show full filename of artifacts as its too long, so that might be part of the problem as users would not be seeing the android-* and architecture tags at the end. The release artifacts default sort order can't be changed either to list universal architecture apk first. The downloads section shows the full name and lists universal apk first to solve those issues. Will have to automate that with github workflow as manually creating the section is cumbersome.

https://github.com/termux/termux-app/releases/tag/v0.119.0-beta.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants