# Troubleshooting for Android

> Solve common issues when developing for Android using Unity.

Learn how to resolve common issues when developing Android applications using Unity.

## Android manifest file contains unexpected permissions

When building a Unity Android application, the final application manifest might contain permissions that you didn't explicitly add to your project. Such unexpected permissions might cause issues when you want to distribute your application through distribution services, such as the Play Store.

### Symptom

The application manifest contains unexpected permission entries that aren't part of your project's manifest files.

### Cause

When building a Unity Android application, Gradle generates the final application manifest by merging manifest files from various sources including plug-ins and packages. This process might automatically include certain unexpected permissions in the manifest based on the dependencies and the target SDK version.

### Resolution

To identify and resolve such unexpected permissions, use the manifest merger log file that Gradle generates when you [build your Android application](/engine/6000.6/manual/platform-specific/android/building-and-delivering/build-process.md). This log file provides information on how and why Gradle adds each manifest element. Follow these steps:

1. Build your application in `.apk` or `.aab` format.

2. Go to the `logs` directory under `<your_project>/Library/Bee/Android/Prj/IL2CPP/Gradle/launcher/build/outputs`.

3. Open the appropriate log file based on the build type.

   * **Release build**: `manifest-merger-release-report.txt`
   * Development build: `manifest-merger-debug-report.txt`

4. Look for log entries that start with `IMPLIED` to identify unexpected permissions. The log file displays information as follows:

   ```
   IMPLIED from D:\MyProject\Library\Bee\Android\Prj\IL2CPP\Gradle\launcher\src\main\AndroidManifest.xml:2:1-5:12 reason: com.test.package has a targetSdkVersion < 4
   uses-permission#android.permission.READ_PHONE_STATE
   ```

5. Check the `reason` field to identify the cause of the unexpected permission. In this example, the log entry indicates that Gradle added the `uses-permission#android.permission.READ_PHONE_STATE` permission because the `targetSdkVersion` of the `com.test.package` is lower than `4`.

6. Contact the owner of the package to request updating the target SDK version to match your project's target SDK version.

## Additional resources

* [Debug on Android devices](/engine/6000.6/manual/platform-specific/android/developing/testing-and-debugging/debugging-on-an-android-device.md)
* [Android App Manifest](/engine/6000.6/manual/platform-specific/android/introducing/manifest.md)
* [Troubleshooting Gradle build issues for Android](/engine/6000.6/manual/platform-specific/android/introducing/gradle-overview/troubleshooting.md)