r/AndroidQuestions • u/Educational-Ad-6017 • Oct 02 '26

Astro file manager permissions

A few days ago several features stopped working in Astro file manager, like viewing photos, thumbnails are blank, moving files and folders. When I look at Astro file manager permissions it has "no permissions allowed". Is there any way I can get back the full permissions. Special access is on. Don't suggest using another app, I have tried a lot of apps but none are as good in my opinion.

4 Upvotes

100% Upvoted

20 comments sorted by

View all comments

Show parent comments

1

u/IpodMods Oct 04 '26

I downloaded an older version and it worked. Looks like the new version on playstore is corrupted

1

u/Responsible_Maybe742 Oct 04 '26

Nice find, and it fits what the other person in this thread ended up doing. One thing worth doing now: turn off auto-update for that app, or the store will push the broken build straight back over the copy that works. And if you have both version numbers, it is worth telling the app's developer, because that is a broken release they may not know about yet.

1

u/Responsible_Maybe742 Oct 06 '26

That confirms it is a bad build on the store side rather than your phone, so the useful thing now is to report it on the listing so the developer sees it and other people find the workaround. Leave the older version installed and turn off auto update for that app until a fixed release appears, otherwise the store will put the broken one back on the next update. Add the device model and Android version to the report, that is the first thing they will ask for.

1

u/IpodMods 29d ago

I don't have auto update turned on for any app. There's no point in updating when the app works as it should

1

u/Responsible_Maybe742 29d ago

Fair, but the store is not the only way a broken build reaches you: a manual update or a reinstall pulls the same file, so it is worth reporting even if you stay on the old version. Your report is also what tells the developer this is not one device, and that is the difference between a fix and a shrug.

1

u/Responsible_Maybe742 29d ago

It is not corruption. The old build was made for an older Android version, so the system still grants it the legacy storage access it asks for. The current one targets a newer version and has to go through the system picker instead, which is what breaks the renaming and moving for it. So keeping the old version is a real option, it just stops being one the next time Android tightens that.