[Bug] App unusable, keeps spamming "added to queue"

[GfEW]

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

I haven't understood exactly how to reproduce the problem, so I just describe it below. It is so severe I've had to resort to the original F-Droid app, only checking NeoStore once a month for the remote hope it might become usable again.

On each of my devices, there are a few dozen apps from alternative stores (mostly f-droid). The major upgrade to 1.0.x has made updating with NeoStore very slow on all of them (see also #593). Watching for the next app's update dialog to finally appear got so time consuming I often had to leave in the middle of the process, when e. g. 20 of 23 app still remained to be updated. Over time, more and more stalled/incomplete updates have piled up, including multiple versions of some apps.

Now, whenever NeoStore is launched, it takes a moment to settle, then starts to issue a toast message reading "added to queue" every few seconds. That message is repeated virtually endlessly, even after many hours, without change of content or frequency. The interval is roughly 5 s, so if every "added to queue" denotes a distinct install task, App Manager's queue gets stuffed with about 720 update tasks per hour.

I can't even work in other apps meanwhile, because those messages keep stealing focus.

The only way I know to stop them is to force-stop NeoStore. Then, the next time NeoStore is launched, one update dialog actually appears, and that single app can be updated successfully. After that, the "added to queue" spam continues.

Expected Behavior

For every updatable app, NeoStore should fetch the update in reasonable time, then add it to App Manager's install queue only once.

Neo Store's Version

1.0.5

Installation Source

Official F-Droid repo

Last Known Working Version

Not sure, but never had this issue with pre-1.0.0.
Also, updates work fine in the original F-Droid app (23 updates take less than 20 minutes).

Relevant information

• Device: diverse
• Android Version: 9 to 11
• ROM: (AOSP, CalyxOS, MIUI, GOS...): stock
• Disabled battery optimization for Neo Store?: yes
• What is your selected installer?: App Manager

[machiav3lli]

I'm not sure about the slowness (it could be the parallel downloads or that the servers are throatelling certain agents - or both?).

I'm aware of memory issues in 1.0.X and these were already fixed in the previous 1.0.6 alphas. I'm currently testing the beta which could turn up to be an rc (or even stable release), if test builds pass the community.

On the AM installer issue: I'm aware of an issue with the AM installer logic, but lack any documentation how to handle this better considering lack of full documentation (or maybe an API?). I'd suggest using the default session installer or root generally. And when there's a chance (change of situation) I'll approach the AM installer issue again.

[GfEW]

Thanks for your thoughts and comments.

I'm not sure about the slowness (it could be the parallel downloads or that the servers are throatelling certain agents - or both?).

I have no idea, other than it didn't happen with e. g. 0.9.15, and doesn't with the F-Droid app, either.

I'm aware of memory issues in 1.0.X and these were already fixed in the previous 1.0.6 alphas. I'm currently testing the beta which could turn up to be an rc (or even stable release), if test builds pass the community.

I'm looking forward to it.

On the AM installer issue: I'm aware of an issue with the AM installer logic, but lack any documentation how to handle this better considering lack of full documentation (or maybe an API?). I'd suggest using the default session installer or root generally. And when there's a chance (change of situation) I'll approach the AM installer issue again.

I've given the default session installer a try (no root available ATM). The setting doesn't seem to immediately stop the messages, but once NeoStore has been force-stopped and relaunched, it refrains from resuming them. Working in other apps while waiting for updates is possible again, what a relief.

The update progress (if any) is still unbearably slow, though. One single update dialog (by the session installer) has shown up shortly after relaunching NeoStore and tapping Install all, but it's been 3 hours since and I'm still waiting for the next update dialog (out of 35, this time) to appear. There's no error message nor any other indication of what's going wrong.