Search Issue Tracker

By Design

Votes

1

Found in

2022.2.0b3

2023.1.0a4

Issue ID

UUM-10962

Regression

Yes

[Android] Build fails with the error "Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8" when project has a custom Manifest

--

-

# Open the attached "NotchSafeAreaSample.zip" project
# Go to File > Build Settings
# Make sure that the Android Platform is selected
# Build and Run

Expected result: Build is successful
Actual result: Build fails with a failure message:
{code:java}
A failure occurred while executing com.android.build.gradle.tasks.ProcessLibraryMAnifest$ProcessLibWorkAction
{code}
and errors:
{code:java}
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
{code}
{code:java}
CommandInvokationFailure: Gradle build failed.
{code}
Reproducible with: 2022.2.0a18, 2022.2.0b3, 2023.2.0a4
Not reproducible with: 2020.3.37f1, 2021.3.8f1, 2022.1.12f1, 2022.1.12f1, 2022.2.0a17

Notes:
- Workaround for the issue is to add in the 4th line of "AndroidManifest.xml"
{code:java}
android:exported="true{code}

- Tested on MacBook Pro, Chip Apple M1 Max

  1. Resolution Note:

    `android:exported` is required by Android when the activity has an intent-filter. The error does not happen when using a templated custom Manifest, only if the user modifies it and adds an intent-filter.

Log in to vote on this issue

Comments (3)

  1. tibtibc

    Mar 03, 2023 05:53

    The same for me... Even after adding android:exported="true"

  2. JuliusM

    Jan 03, 2023 11:19

    IMRANKARIMI009, add android:exported="true" attribute to all of activities with intent filters in your custom manifest file.

  3. imrankarimi009

    Jan 01, 2023 20:06

    I am facing same issue on unity 2022.2.1f1 do you have any solution to fix this?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues