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

Issues with AppCleaner on a non-root device #2695

Closed
antonio-gil opened this issue Jun 11, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@antonio-gil
Copy link

commented Jun 11, 2019

What happened?

Whenever I try to clear the caches, it seems ("behind" the overlay) that the Accessibility service successfully opens the "App Info" section, but it doesn't do anything there. Actually, it opens the "App Info" section a couple of times (ten times, if I'm counting correctly) before continuing to the next application on the list. And, I'm assuming that it is not doing anything because the cache size is the same after the process is done than it was before. Also, I've noticed that sometimes, by some unknown reason the process finished abruptly, and the Accessibility Service is disabled.

(The last part was already clarified on the SDMaid subreddit, but I'm mentioning it here for the sake of completeness)

What did you expect to happen?

That the application's cache were deleted according to the current configuration.

What actions did you take?

This happens whenever I run the AppCleaner module individually, or when running the QuickAccess operations.

Can you reproduce it, i.e. does this happen everytime?

Yes, this happens every time.

Additionally, I take a look into the log, and something that I noticed is that (if I understandit correctly) it seems that there's a small discrepancy regarding the expected option (Storage) and the existing one (Storage space). Of course, I could be misinterpreting what I saw, but I got curious about it.


Additional Info:

Device: Nokia 3.1
Android version: Stock Android One 9
Root: Unavailable
SD Maid / SD Maid Pro version: SD Maid v4.14.21, Unlocker v4.3.8
Install ID: 8e69d020-1539-4abd-b200-417eceff5b2d
Debug Log: sdmaid_logfile_1560215854679.txt.zip
Video: recording_20190610_201744.zip (Disclaimer: It's an MP4 file, but I couldn't upload it as it is here, so I zipped it. Also, I really don't know why, but although it looks good on my device, on my computer it looks weird (as if a duplicated of the video was appended to the bottom of the video), nonetheless, the issue is visible). Also, I attach an screenshot taken after the video was recorded (you can check the clock), and the information on the AppCleaner module was refreshed (doing a "pulling down") in order to show that the cache size is still the same.

@d4rken d4rken added this to the v4.14.23 milestone Jun 11, 2019

@d4rken

This comment has been minimized.

Copy link
Owner

commented Jun 11, 2019

Actually, it opens the "App Info" section a couple of times (ten times, if I'm counting correctly) before continuing to the next application on the list.

SD Maid's retry+timeout mechanism.

Additionally, I take a look into the log, and something that I noticed is that (if I understandit correctly) it seems that there's a small discrepancy regarding the expected option (Storage) and the existing one (Storage space). Of course, I could be misinterpreting what I saw, but I got curious about it.

That's exactly what it is. 👍 Interesting that this is a stock ROM, as there is also a typo 😲, a missing space after the size.

Screenshot from 2019-06-11 11-58-23

Can you check whether the storage page's Clear cache is named exactly that? Maybe post a screenshot of that too. Would suck if I update for this only for SD Maid to be stuck on the next page 😉

btw, love the detailed ticket.

@antonio-gil

This comment has been minimized.

Copy link
Author

commented Jun 11, 2019

Hi!

As requested, here is the requested screenshot:

If you need something else, please let me know.

Interesting that this is a stock ROM, as there is also a typo 😲

Haha I didn't noticed that! I guess that the guys on HDM Global didn't pay enough attention to that.

btw, love the detailed ticket.

Thank you sir! Glad to know that it was helpful 😁

@d4rken

This comment has been minimized.

Copy link
Owner

commented Jun 11, 2019

Thanks, will be fixed in the next update.

@d4rken d4rken closed this Jun 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.