Package	com.myflashlab.air.extensions.nativePermissions
Class	public class PermissionCheck
Inheritance	PermissionCheck Object

PermissionCheck class lets you check if your app has access to a specific hardware or a native feature that is considered dangerous by the OS. Dangerous permissions are those that may deal with users privacy context.

Prior to Android 6.0, you just needed to ask for permissions in the manifest .xml file but that is changed now and Android is asking for dangerous permissions in runtime, similar to how it has been working on iOS.

iOS: Considering that permissions work a bit different on the iOS side compared to the Android side, You should know the difference in details in order to be able to build your UI. Below is how you should work with permissions on the iOS side:

• Check if your app has permission to a feature; For example the camera.
• If this is the first time you are checking, it will return PERMISSION_UNKNOWN
• Only and only if the permission state is PermissionCheck.PERMISSION_UNKNOWN you can request for that feature.
• When you send a request, a native dialog will be shown to the user so she can decide if she wants your app to have access to camera or not.
• No matter which option she chooses, you can never again ask for that permission explicitly. You can only check if that permission is granted or not.
• If your app functionality relies on having access to camera, you should promote the user to allow access to that by going to the apps settings menu
• When you are in the apps settings menu, you can change how the permission settings are and as soon as you do that, iOS OS will automatically force close your app to take into effect the changes

Android: unlike the iOS side, working with permissions on Android is more dynamic. Here's how it works:

• Check if your app has permission to a feature; For example the camera.
• If this is the first time you are checking, it will return PERMISSION_DENIED
• Only if the permission state is PermissionCheck.PERMISSION_DENIED you can request for that feature.
• If user has already granted you the access, requesting for that feature will not open the permission dialog again.
• When you send a request, a native dialog will be shown to the user so she can decide if she wants your app to have access to the camera harware or not.
• If access to the feature is denied, you can still request for the permission and the dialog window will be opened
• Like the iOS side, the ANE has a method for you to easily open the app settings menu so the user can see the list of features that the app has access to.

Dangerous permissions on iOS supported by this ANE:

• CAMERA
• MIC
• CONTACTS
• CALENDAR
• PHOTOS
• REMINDER
• LOCATION_WHEN_IN_USE
• LOCATION_ALWAYS

Dangerous permissions on Android supported by this ANE:

• CAMERA
• MIC
• CONTACTS
• CALENDAR
• PHONE
• STORAGE
• LOCATION
• SENSORS
• SMS

---

         import com.myflashlab.air.extensions.nativePermissions.PermissionCheck;
                  PermissionCheck.init();
         var permissionState:int = PermissionCheck.check(PermissionCheck.SOURCE_CAMERA);
                  // If this is the first time you are trying to access a feature, the iOS side will return PERMISSION_UNKNOWN
         // but the Android side returns PERMISSION_DENIED.
         if(permissionState == PermissionCheck.PERMISSION_UNKNOWN || permissionState == PermissionCheck.PERMISSION_DENIED)
         {
             PermissionCheck.request(PermissionCheck.SOURCE_CAMERA, onRequestResult);
         }
                  private function onRequestResult($obj:Object):void
         {
             // $obj.source indicates the permission you have requested
             // $obj.state is either PERMISSION_DENIED or PERMISSION_GRANTED
         }
         

         private function onRequestResult($state:int):void
         {
             // $state is either PERMISSION_DENIED or PERMISSION_GRANTED
             trace($state)
         }