Declare Storage Permissions in the Manifest

[bodymindpower (Anke)]

Here is an extension, that declares storage permissions (READ & WRITE) correctly in the Manifest:
DeclareReadWrite.aix (4.7 KB)

<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="29" />

Since many components don’t declare storage permissions anymore after der 1.5.5 update, use this extension.

Even if your app doesn’t need these permissions, it’s harmless and has no disadvantages. But without declaring permissions in the Manifest, they cannot be requested (neither at runtime on Android 6+ nor at install-time on Android < 6).

[bodymindpower (Anke)]

[S_Vicky (Dr Vicky)]

How to use this extension. Please share blocks.Thanks

[bodymindpower (Anke)]

@S_Vicky

Please share blocks.

See above.

@S_Vicky

How to use this extension.

Drag it into the Designer. That’s all.

[Current_Affaires_com]

What about Android 11 it’s not working on it.

[Current_Affaires_com]

Shouldn’t we use blocks ? Ask permission?

[S_Vicky (Dr Vicky)]

I am unable to get you. Please can you share the blocks on designer?

[bodymindpower (Anke)]

@Current_Affaires_com

Shouldn’t we use blocks ?

There is only one block:

@Current_Affaires_com

Ask permission?

Kodular Fenix 1.5.5 Bug Tracker

Many storage permission bugs / issues can be fixed if these permissions are correctly declared in the Manifest. Here’s an extension that does it: Whether the permissions are then automatically requested depends on the respective components and must be checked (with the APK). So if you found a permission problem, use this extension and report back if the problem persists.

[bodymindpower (Anke)]

@S_Vicky

Please can you share the blocks on designer?

[bodymindpower (Anke)]

@Current_Affaires_com

What about Android 11 it’s not working on it

What is not working?
On Android 11+ WRITE permission does no longer exist and therefore it cannot be granted on Android 11.

[roneylima1992]

Is it only necessary to insert the extension? Don’t need to modify anything in the blocks?

[bodymindpower (Anke)]

@roneylima1992

Is it only necessary to insert the extension?

Yes.

@roneylima1992

Don’t need to modify anything in the blocks?

There is nothing to modify!
As I said, there is only 1 block (and this helps to get the API of the device).

[roneylima1992]

@bodymindpower

There is nothing to modify!
As I said, there is only 1 block (and this helps to get the API of the device).

I inserted the extension in my project, but the bug continues, I can’t download it through the apk.

[bodymindpower (Anke)]

@roneylima1992

I inserted the extension in my project, but the bug continues

Kodular Fenix 1.5.5 Bug Tracker

Many storage permission bugs / issues can be fixed if these permissions are correctly declared in the Manifest. Here’s an extension that does it: Whether the permissions are then automatically requested depends on the respective components and must be checked (with the APK). So if you found a permission problem, use this extension and report back if the problem persists.

Kodular Fenix 1.5.5 Bug Tracker

The Download component incorrectly requests WRITE permission also on Android 11+. Since a file is downloaded to the Shared folder /Download, no storage permissions are required on Android 11+.

[hammerhai (Nathan)]

Wondering how you defined android:maxSdkVersion="29" considering there’s no annotation member for this in App Inventor.

[S_Vicky (Dr Vicky)]

Not working. Still The same issue

[bodymindpower (Anke)]

@S_Vicky

Not working. Still The same

Post the APK.

[bodymindpower (Anke)]

WRITE is still declared only up to API 29 (Android 10).

Read my answers carefully …

[S_Vicky (Dr Vicky)]

Thanks
Now whats the solution?

[bodymindpower (Anke)]

See e.g. here:

Denied permissions in advance After updating the version to (Kodular Fenix 1.5.5)

[grafik] If so (as I mentioned several times), build the APK, decompile it and edit the Manifest by declaring this line in the Manifest, recompile and try again. [grafik] Which means that now WRITE is incorrectly also declared on Android 11+ (but it can never be granted there, as it works the same way as READ on Android 11+). This is of course (as also mentioned several times) a bug! But it should solve your problem until this serious bug is (hopefully soon) fixed.