tareksander

I read the f-droid docs further and apparently it generates a signing key for each application, but that can be overwritten. That seems to be set up for the other...

I moved the repo now. I already have a PR open at f-droid for this and updated the repo URL, and I can link this thread if they want proof...

> @tareksander This needs a fix: > > https://github.com/termux/termux-gui/blob/f8abd21af5dc2676a82055b4285f5ddeca409440/app/build.gradle#L44-L49 > > You are using ~leaked~ development key for release signature. I fixed that now, but I don't think that solves...

I have [this MR](https://gitlab.com/fdroid/fdroiddata/-/merge_requests/10240) over at f-droid. It seems signing apps with the same key can't be done with the metadata and requires special handling in the signing process.

I have the same problem with `micro`, I just configured an extra key to show/hide the keyboard.

Debug builds in Github Actions eventually expire, it would be nice if there was a dedicated repo to uploading the debug builds as releases (to not mess with f-droid picking...

Do you need any more features than already implemented in #475 ? You can get documentation for each of the `termux-saf-*` commands with the -h option.

It is implemented, but there wasn't a release since it was implemented. I don't know if termux-saf-* is included in the package yet since they won't work, but you can...

It won't work unless you use the github builds, where the functionality is already implemented

Yes, Termux and all plugins must be installed from the same source.