Android Question permission not showing in permission list

[buras3]

Hello

i need help with this
the permission is exist in the manafest file

PERMISSION "PERMISSION_WRITE_CONTACTS" not showing in permission list

the dialog is not firing when rp.CheckAndRequest(rp.PERMISSION_WRITE_CONTACTS) called

 

[DonManfred]

the permission is exist in the manafest file

where is your manifestcontent? You did not post it.

 

[buras3]

'This code will be applied to the manifest file during compilation.
'You do not need to modify it in most cases.
'See this link for for more information: http://www.b4x.com/forum/showthread.php?p=78136
AddManifestText(
<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="26"/>
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"/>

)
AddManifestText(<uses-permission
android:name="android.permission.WRITE_EXTERNAL_STORAGE"
android:maxSdkVersion="18" />
)
'    <uses-permission android:name="android.permission.INTERNET"/>
'    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
CreateResourceFromFile(Macro, FirebaseAnalytics.GooglePlayBase)
CreateResourceFromFile(Macro, FirebaseAnalytics.Firebase)
CreateResourceFromFile(Macro, FirebaseAnalytics.FirebaseAnalytics)
CreateResourceFromFile(Macro, FirebaseAdMob.FirebaseAds)
AddPermission(android.permission.READ_CONTACTS)
AddPermission(android.permission.WRITE_CONTACTS)

 

[DonManfred]

Did you scroll to the bottom in the list of permissions????

 

[DonManfred]

AddPermission(android.permission.READ_CONTACTS)
AddPermission(android.permission.WRITE_CONTACTS)

look at the COMPLETE list first.... Based on your screenshot there is a permission out of the view....

Scroll the list to see all entries.. Or make the window larger...

 

[buras3]

 

[DonManfred]

So IT IS in the list! You can mark this thread as SOLVED.

What is your question now?

 

[buras3]

in a smiler app with same libraries i have this

but not in the new one

 

[DonManfred]

It is a new question (new issue). Please create a new thread for any new question.

I´m not interested to ask more questions just to find out you did not checked the list completely again...

Check the hole list first. If it does not work as expected; upload a example project which shows the issue.

 

[buras3]

please add me to your ignore list again
i need help from other users

 

[DonManfred]

And you think you´ll get other answers if you JUST DID NOT checked the permissionlist carefully?

Yes, don´t expect any more answers from me!

 

[buras3]

same problem
https://www.b4x.com/android/forum/threads/several-runtime-permissions.95583/#content

 

[Semen Matusovskiy]

When you use libraries, B4A simply looks <permission> tags in XML-file.
If author of library forgot to add permissions, you will not see them in the list of permissions.

I wrote small 'library' as example and compiled it in SLC.

package b4a.SM.Test;

import anywheresoftware.b4a.BA;
import anywheresoftware.b4a.BA.Permissions;

@BA.Version (1.00f)
@BA.ShortName ("smTest")
@Permissions(values={"android.permission.SEND_SMS"})
@BA.ActivityObject

public class smTest
    {
    public static void Initialize (BA ba, String eventName)
        {
        }
    }

If to include my library into B4A project, IDE will show that app requires android.permission.SEND_SMS permission.
Meanwhile permissions are not necessary at all.


About read_contacts / write_contacts and similar.
Many persons think that it's enough to include one permission from group and other permissions from this group will work also. It's true for some Android API releases. But documentation talks.

Your app still needs to explicitly request every permission it needs, even if the user has already granted another permission in the same group. In addition, the grouping of permissions into groups may change in future Android releases. Your code shouldn't have logic that depends on a set of particular permissions being in the same group.