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

Suggests to update version 1.2 to 1.1 #1899

Open
sphh opened this issue Oct 10, 2024 · 4 comments
Open

Suggests to update version 1.2 to 1.1 #1899

sphh opened this issue Oct 10, 2024 · 4 comments
Labels
enhancement New feature or request source-specific This bug/feature affects a specific source

Comments

@sphh
Copy link

sphh commented Oct 10, 2024

Describe the bug

I have OneTimeAlarm v. 1.2 installed (from F-Droid). I then added https://github.com/matdlu/OneTimeAlarm/ to Obtainium. I always get an update information, that version 1.2 is installed, but 1.1 is available. After some investigation I noticed, that the release page has only the version 1.1, but the tags page has the versions 1.0, 1.1 and 1.2.

To Reproduce

  1. Install latest version of OneTimeAlarm (v. 1.2).
  2. Add OneTimeAlarm to Optainium.
  3. Update Optainium.
  4. Optainium show current version as 1.2, but suggests to update to version 1.1.

Please complete the following information:

  • Device: Unihertz Jelly Pro
  • OS: Android 8.1
  • Obtainium Version: 1.1.26
@sphh sphh added bug Something isn't working to check Issue has not been reviewed labels Oct 10, 2024
@DarkCrypt
Copy link

Obtainium recognizes v1.1 as the latest release because there's no apk to download for v1.2.

If you toggle off "Reconcile version string with version detected from OS" then hit the check mark and "Mark as Updated", this will stop the update notification but the version will still say v1.1.

FYI, there has been no future update for OneTimeAlarm since Aug 2022.

@sphh
Copy link
Author

sphh commented Oct 12, 2024

Ah, I see: Obtainium only looks at releases, which actually have an .apk file ‘attached’?
I can understand the reasoning behind this, still it is a bit weird, that it suggests to update from version 1.2 up to 1.1 …

Would an option to remove the apk-check make sense for Track only entries? E.g. if one wants to (or has to) compile the app oneself?

@ImranR98
Copy link
Owner

Yes track-only already does that.

@ImranR98
Copy link
Owner

Nvm, it only does that if there are no releases at all. I guess we could add an option to use tags.

@ImranR98 ImranR98 added enhancement New feature or request source-specific This bug/feature affects a specific source and removed bug Something isn't working to check Issue has not been reviewed labels Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request source-specific This bug/feature affects a specific source
Projects
None yet
Development

No branches or pull requests

3 participants