I added an extension in a screen which uses permission like write_exteternal_storage etc. then checked the apk, yes permission is there, then I removed that extension from screen and deleted from the project and built the apk, the permission is still there! Why the permission is not removed? You know this can cause app/account suspension on play store?
There might be other components or extensions in your project that requires wirte_external_storage permission.
Yes it is required.
But if image picture is used from assets then this permission must not be there!
There are components that uses those permissions Read and Write. Not just images, Read and Write is not a dangerous permission.
Read and Write permissions works only on android version < 11
SEE MY FRIEND >>>This is a dangerous permission
Lol! ListView also request this dangerous permission!
If we ignore and build apps including such irrelevant permissions which have no connection with our app’s functionality then Google will suspend our apps/account! Just for these silly things and Google will never tell you the reason because those are bots which take action while reviewing the apps.
I have not published the app on Playstore yet. Do you have any solution?
.
For example if you are using image component to just show your app icon on login screen. So you will set picture from your app’s assets. Image component if used include read external storage permission, but actually app is not reading external storage.
I used a vertical arrangement and set image for it, so image is showing without using image component and read external storage permission is removed now, this is how I solved this issue.
Same problem is associated with listview, therefore I used ListPicker instead of listview to get rid of read external storage permission.
1 Like
You can actually edit your app Manifest using apk editor to remove the permissions you don’t want.
1 Like
after editing the manifest file, how to recompile it? if there is a tool. please provide the link.
1 Like
If I add features to the app that justify the permissions can I solve the issue?
instead of reverse engineering. 
1 Like
Only APK tool or APK editor is not for Play store apps, it won’t provide you .aab file. Why people are using Niotron or other platforms (no code app development) if they are required such advance editing APK, Decompile, Recomplie, apk 2 aab & so on…? They should get feature to remove unwanted permissions in builder itself in simple form so that it will be very systematic approach.
There are tools to convert .apk to .aab
& Who will be responsible if any tool make any loss?