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

Neo Store cannot update itself #614

Open
Smutley opened this issue May 20, 2024 · 10 comments
Open

Neo Store cannot update itself #614

Smutley opened this issue May 20, 2024 · 10 comments

Comments

@Smutley
Copy link

Smutley commented May 20, 2024

I just started using Neo Store at version 1.00. In the subsequent two new versions, 1.01, and 1.02, I have observed that Neo Store cannot update itself to the newer version. It appears to download, but then simply stops. One has to install F-Droid in order to update Neo Store.

Android 13 on Pixel 8.

This issue is also observed on two other Xiaomi phones I use.

Expected behavior - Neo Store should not require another app to update; it should be able to update itself.

@Smutley
Copy link
Author

Smutley commented May 20, 2024

That should be Android 14 on Pixel 8, not Android 13.

Xiaomi phones are Redmi Note 11s, running Lineage OS 13, and Evolution X 13.

@machiav3lli
Copy link
Member

I guess you have the download stuck or something in that direction (try deleting the item in the downloaded list and sync) …
Here's some needed information:

  • Did you disable battery optimization for NS?
  • Is the auto-update enabled?
  • Did other apps get updated?
  • What is your selected installer?

@Smutley
Copy link
Author

Smutley commented May 20, 2024

Thank you for replying.

I did delete the downloaded update; rebooted, with no luck. However, I did not try to re-sync because the new version showed as available (manual install), and or immediately attempted to download and install. No joy.

  1. Yes, battery optimization is disabled for Neo Store.
  2. It would not update under auto-update, or under manual.
  3. Other apps update fine.
  4. I only used the root installer on all devices.

@machiav3lli
Copy link
Member

Can you try installing the latest version through tapping the install button on the suggested version at the bottom of the app sheet?

@opusforlife2
Copy link

opusforlife2 commented May 24, 2024

@machiav3lli Found the bug. I navigated to the folder where Neo Store caches the downloaded APKs. The APK was incorrectly downloaded/corrupted in some manner. Tapping on it caused the "There was a problem parsing this package" dialogue.

The APK can be deleted manually or by clearing the cache. But re-downloading keeps giving the same broken APK.

^ Incorrect. See: #614 (comment).

I'm trying to update from 1.0.1 -> 1.0.2. Didn't face this bug in previous updates.

BTW, the rest of the apps download and update just fine, though this is the same repo index update cycle. It is only Neo Store itself which has a corrupt APK when self-downloading. Also, APKs downloaded from Github and F-Droid's website are parsed perfectly fine.

On a hunch, tried toggling the System download manager off and on. That didn't work. This happened on multiple devices so the bug is surely in Neo Store.

@opusforlife2
Copy link

@machiav3lli Do you want to do any tests? I'm still on 1.0.1 just in case you do.

@machiav3lli
Copy link
Member

@opusforlife2 using system download manager or the default downloader?

@opusforlife2
Copy link

On a hunch, tried toggling the System download manager off and on. That didn't work.

^

I normally use system, not default. But this bug seems to be occurring for both.

@opusforlife2
Copy link

opusforlife2 commented Jun 2, 2024

Update: Apparently, the non-parsable APK in the cache folder wasn't necessarily broken, because ALL APKs seem to be in the same state, even if the apps/updates install successfully.

So Neo Store is simply not carrying out the install step for some reason. I also tried this with the default session installer.

Edit: Also, this bug is a bit random, because it is happening on two devices with LOS 21, but not on two others, also with the exact same OS and general settings.

@crystalcommunication
Copy link

I am experoencing this issue on every device on which I happened to upgrade to version 1.0.1. Upgrading to version 1.0.2 does not seem to fix it. I used a different F-Droid client to upgrade Neo Store and then told Neo Store to reinstall itself. On other devices upon which I upgraded directly from Neo Store 1.0.0 to 1.0.2, the issue did not occur, and Neo Store 1.0.2 reinstalled itself when requested. All devices were running LineageOS 21 or 20 and the root session installer method.

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

4 participants