Permissions

Android

The Android SDK includes its own AndroidManifest.xml file that will merge with your application’s manifest. Accordingly, all required permissions will be automatically included.

For clarity and transparency, below you’ll find a list of the permissions that are required and their use case:

    // Networking
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
    
    // Voice messages
    <uses-permission android:name="android.permission.RECORD_AUDIO" />
    <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
    
    // Background work
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <uses-permission android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" />
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
    
    // Working with bluetooth accessories
    <uses-permission android:name="android.permission.BLUETOOTH" />
    <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
    <uses-permission
		android:name="android.permission.BLUETOOTH_SCAN"
		android:usesPermissionFlags="neverForLocation"
		tools:targetApi="s" />
        
    // Android 14+ foreground service types
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK" />
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_MICROPHONE" />
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_LOCATION" />
	
    // Used for location messages, as well as our geotracking "Map" feature available through the Zello Work console.
    // Additionally, used for Bluetooth scanning
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
	
    // Vibrating the phone when a message is received
    <uses-permission android:name="android.permission.VIBRATE" />
	
    // Android 7 permissions to store history. Not needed if your app targets Android 8+
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
	
    <uses-feature
        android:name="android.hardware.microphone"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.wifi"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.bluetooth"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.bluetooth_le"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.location"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.location.gps"
        android:required="false" />
    <uses-feature
        android:name="android.hardware.location.network"
        android:required="false" />

You will need to request these permissions (audio, post notifications, location, bluetooth) wherever it makes sense for your application, but before you use these Zello SDK features.

Although the SDK does not include the permission ACCESS_BACKGROUND_LOCATION by default, you may choose to add it to your manifest. It must be granted for location services to work in cases where your app is signing into the SDK while running in the background.

iOS

The iOS SDK uses the following permissions:

1. Notifications

2. Microphone

   1. Sending audio messages

3. Bluetooth

   1. Connecting to bluetooth accessories

4. Location

   1. Location messages, as well as our geotracking "Map" feature available through the Zello Work console.

After the notifications permission has been granted, call the Zello.registerForRemoteNotifications(deviceToken:) function.