[Request] Select the correct APK by signing key
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by examining the UI that shows the installed version and the warning about differing signing keys, then trace how the app identifies the installed APK and presents available APKs. The request leaves open whether the goal is automatic selection, showing the installed APK's fingerprint, or both; clarify the expected behavior before estimating completion.
Written by the indexing model from the issue text.
Description
Guidelines
- I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
- I'm not requesting app support for a specific repo — that's up to repo maintainers
- I understand this might not get built (Droid-ify is maintained by a single person)
Problem
I just ran into this with: https://f-droid.org/packages/juloo.keyboard2/
There are apparently now two APKs available, the one from the author had a different signing key. The UI presented a nice warning about that, thanks!
Proposed solution
I'd very much like the software to figure this out and choose the correct signing key based on the already installed APK.
At the very least, it would help immensely if the version marked as installed included the fingerprint also.
Extras
No response
- Dominant language
- Kotlin
- Stars
- 7.7k
- Forks
- 233
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Droid-ify/client
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in Droid-ify/client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
afk-ok area:ci size:S
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
enorm-labs/event-junkie#4518 ·
Maintainers usually reply within 1 day
-
android:player
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
confluentinc/intellij#670 · 1 comment ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NucleusFramework/Nucleus#912 ·
Maintainers usually reply within 1 day