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

[Still-learning (1-2-3-4...)]

Declare Storage Permissions in the Manifest - #15 by bodymindpower…

…
Read this

[tru_mm]

Ok, I have added the DeclareReadWrite.aix extension to the application and the problem is still there
Can you share how the block works for this extension?

[bodymindpower (Anke)]

@tru_mm

I have added the DeclareReadWrite.aix extension to the application and the problem is still there
Can you share how the block works for this extension?

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.

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.

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.

[tru_mm]

[bodymindpower (Anke)]

Please read my answer carefully, then you wouldn’t be asking this question.

[bodymindpower (Anke)]

How to customize the Manifest → example: Companion APK

Here’s a quick guide on how to customize the Manifest (→ APK Studio Editor or A2M): Decompile the APK open the Manifest: AndroidManifest.xml edit the Manifest Recompile the APK Done in less than 1 min!

[tru_mm]

Well I will try this

[tru_mm]

I can try it now

[bodymindpower (Anke)]

[S_Vicky (Dr Vicky)]

Thanks Now cleared.

[tru_mm]

Yes, thanks, it worked
you are the greatest
But another question for (onesignal)
Is there a solution other than using this site?

Enhance Your App

[tru_mm]

Well I found the solution for this too here

[BETA] OneSignal Fix Extension

[icon] OneSignal Fix Hello everyone, as we know since kodular last update push notification component stopped working after target SDK to 30. So from many days I am trying to solve this issue and today finally I solved it and all works fine now I think. This extension fix the one-signal subscription issue by some SDK updates. This is an empty extension mean it has no blocks. It just do the SDK thing in our apps and help onesignal to use the FCM library. This extension is currently in BETA phase…

[tru_mm]

This post was flagged by the community and is temporarily hidden.

[S_Vicky (Dr Vicky)]

My apk manifest already have this permission code but still problem is same

[Johannes_Ai2]

Post the APK and the manifest.

[S_Vicky (Dr Vicky)]

VetmyUpdate (11) (6).apk

[Johannes_Ai2]

Try this one:

VetmyUpdate_2.apk

[S_Vicky (Dr Vicky)]

Hey please tell how you do this beacuse i have to do testing regulary

[Johannes_Ai2]

@S_Vicky

please tell how you do this

As Anke (bodymindpower) has already explained several times, WRITE permission must also (incorrectly) be declared in the manifest on Android 11+. Of course this is a bug that needs to be fixed. Btw, the same problem is with AI2.

Search the AI2 forum and you will find dozens of topics, posts, guides by Anke on this issue.

[Yash_Agarwal]

But i think kodular fixed that issue, right ?
See when i open the manifest it shows permission like this -

So, now do you think we still need to make any changes or use any extension to declare permission in manifest ? @Johannes_Ai2 @bodymindpower