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

[Bug] Some apps can't update, keeps showing "New versions available" for months #673

Open
4 tasks done
WofWca opened this issue Oct 26, 2024 · 7 comments
Open
4 tasks done

Comments

@WofWca
Copy link

WofWca commented Oct 26, 2024

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 on the latest version.
  • I'm not using a test build (alpha/beta/release-candidate).
  • This issue contains only one bug.

Describe the bug

IDK if this is actually reliably reproduces the problem though

  1. Install NeoStore.
  2. Install OONI Probe using NeoStore.
  3. Wait until OONI Probe gets an update in the repository.

NeoStore will update other apps just fine, but for OONI Probe it just keeps showing "New versions available". If I go to "downloads" I see it try to download it, but tapping "Update" on the app's page appears to do nothing.

I observe the same behavior for one other app.

I have tried clearing the download and doing it again.

This has happened for at least 2 versions of OONI probe: 3.9.0 and 4.0.0. I'm stuck on 3.8.9.

Expected Behavior

I am able to update the app

Neo Store's Version

1.0.5

Installation Source

Other…

Last Known Working Version

No response

Relevant information

  • Device: Google Pixel, one of the later ones
  • Android Version: 14
  • ROM: (AOSP, CalyxOS, MIUI, GOS...) GrapheneOS
  • Disabled battery optimization for Neo Store? "Allow background usage" is on. Not sure if that's it
  • What is your selected installer? "Default session installer"
@WofWca
Copy link
Author

WofWca commented Oct 27, 2024

Update: Updating the affected apps with F-Droid worked fine.

@WofWca
Copy link
Author

WofWca commented Nov 11, 2024

Update: another app got an update, and now it's stuck in this state.

@machiav3lli
Copy link
Member

What does "Other…" in installation source means? Did you try cleaning up the cache? Can you please check if the signatures are the same (it could be similar to #659)?

I tested ooni probe (installing 3.8.9 and letting auto-update to 4.0.0 worked just fine.

@WofWca
Copy link
Author

WofWca commented Nov 17, 2024

What does "Other…" in installation source means?

It means I don't remember and I'm not sure how to check 😅
It was probably F-Droid.

Did you try cleaning up the cache?

Yes, I just tried it. I also removed the download.
After a tap to "Download" it downloads the app, but tapping "Update" does nothing.

Can you please check if the signatures are the same (it could be similar to #659)?

I tried disabling signature checking, but the behavior is still the same. Would this suffice?

@WofWca
Copy link
Author

WofWca commented Nov 17, 2024

I've captured some logs, can I send them to you in a personal message? My email is specified in my GitHub profile.

@WofWca
Copy link
Author

WofWca commented Nov 17, 2024

What I noticed in the logs is, it prints:

11-17 18:07:26.634 11821 11844 W ziparchive: Unable to open '/storage/emulated/0/Android/data/com.machiav3lli.fdroid/cache/releases/<app_id>_app_<hash>.apk': No such file or directory

But if I open the file explorer, there is only one file in that directory, for that specific app, but the <hash> part is different. So, is it trying to open the file with a wrong file name?

Update: another thing is that this log message is also printed even for the two apps that do not have updates pending, the ones that I already updates with F-Droid recently (see #673 (comment)). .apks for those files are not in the releases directory.

@WofWca
Copy link
Author

WofWca commented Nov 19, 2024

Update: one of the apps that was in this state and that I later updated with F-Droid before (see #673 (comment)) got another update, and now it's stuck in the "Updates available" state again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants