The React of Native PermissionsAndroid components how to avoid the continuous tip?-CodePudding

 let check1 granted1; 
Check1=await PermissionsAndroid. Check (PermissionsAndroid. PERMISSIONS. ACCESS_COARSE_LOCATION); 
if (! Check1) {
Granted1=await PermissionsAndroid. Request (PermissionsAndroid. PERMISSIONS. ACCESS_COARSE_LOCATION, {
Title: '
The message: 'whether open application network location permissions', 
ButtonNegative: 'NO', 
ButtonPositive: 'YES', 
}); 
}

Tip over 'whether open application network location permissions, point YES, native and prompted again

CodePudding user response:

Generated, the first is the permissions frame as the friendly prompt only (see hungry, taobao, etc., but the somebody else look better interface), if you don't like to look at what frameworks do, oneself change

CodePudding user response:

reference 1/f, wang can reply:

is the first access framework generated, just as a friendly tip (see hungry, taobao, etc., but the somebody else look better interface), if you don't like to look at what frameworks do, to change

But, I'm just in the front of the rn PermissionsAndroid is introduced to operation authorization request, does not write in native requestPermissions these, how could his pop up (figure 2)

CodePudding user response:

This is PermissionsAndroid pop up ah, you pass the code

 if (! Check1) {
Granted1=await PermissionsAndroid. Request (PermissionsAndroid. PERMISSIONS. ACCESS_COARSE_LOCATION, {
Title: '
The message: 'whether open application network location permissions', 
ButtonNegative: 'NO', 
ButtonPositive: 'YES', 
}); 
}

Is not pop up effect, you look at what this code do, there is no other don't need to send this way to know

CodePudding user response:

Now why wouldn't popup window