Microscope

Marque

Instrumentalisation

Disponible immédiatement

À propos de cet article

When developing a native app that requires access to potentially sensitive information on a user's device, such as their location or contacts, the app must request the user's permission first. For example, to access the user's media library, the app will need to run MediaLibrary.requestPermissionsAsync(). Permissions in standalone and development builds require native build-time configuration before they can be requested using runtime JavaScript code. This is not required when testing projects in the Expo Go app.

Permissions are configured with the expo.android.permissions and expo.android.blockedPermissions keys in your app config (app.json, app.config.js). Most permissions are added automatically by libraries that you use in your app either with config plugins or with a package-level AndroidManifest.xml, so you won't often need to use android.permissions to add additional permissions. The only way to remove permissions that are added by package-level AndroidManifest.xml files is to block them with the expo.android.blockedPermissions property. To do this, specify the full permission name; for example, if you want to remove the audio recording permissions added by expo-av:

Connectez-vous pour passer la commande !!!