I do not understand what is the reason. On January 5, I downloaded a new application, everything is fine. Now I decided to update the old one (2 months ago the last time) and gives this: You've uploaded an APK or Android App Bundle with an activity object, object alias, service, or broadcast receiver with intent filter but no android: exported property set. This file cannot be installed on a device running Android version 12 or higher. To find out more, go to developer.android.com/about/versions/12/behavior-changes-12#exported. I added a line to the manifest file, which is mentioned on the site, but it gave nothing. The same mistake. What to do?

Manifest file:

This path: Assets \ Plugins \ Android \ AndroidManifest.xml I added the line mentioned in the article: android: exported= "true", but the same error.

    xmlns: android= "http://schemas.android.com/apk/res/android"
    package= "com.unity3d.player"
    xmlns: tools= "http://schemas.android.com/tools" >
application >
activity android: name= "com.unity3d.player.UnityPlayerActivity"
                  android: exported= "true"
                  android: theme= "@ style /UnityThemeSelector" >
intent-filter >
action android: name= "android.intent.action.MAIN" />
category android: name= "android.intent.category.LAUNCHER" />
/intent-filter >
meta-data android: name= "unityplayer.UnityActivity" android: value= "true" />
/activity >
/application >
/manifest >
Help, please. I tried it in different ways already. Both true and false, but doesn't want to.

A similar situation. The last time I downloaded a new version of the application was on January 11th. Since January 13, when downloading a new version of the Google Play Console, it gives the same error as yours. I noticed that Unity creates the generated AndroidManifest.xml in the project_root\Temp\StagingArea directory during the build, and in it, regardless of what was specified in the Custom Manifest, this line (android:exported) is not present.

Egorqs2022-01-15 03:48:13

Do you still need help? Was able to solve the problem

LittleBob2022-01-14 05:44:16

I rolled back to 30 api, now there are no errors when loading. I hope that soon the unit will add compatibility with new APIs.

Egorqs2022-01-14 13:02:41