'Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present]
While debugging the application in android 12, the app is getting crashed.
Solution 1:[1]
Android 12 require you to add a piece of code to your main activity
Go to your project folder and open AndroidManifest.xml file
Add the below code in activity
android:exported="true"
Example
<activity android:name=".MainActivity" android:exported="true" android:launchMode="singleTop" android:theme="@style/LaunchTheme" </activity>
Solution 2:[2]
In AndroidManifest.xml add android:exported="true":
<manifest ...>
<application ...>
<activity
android:exported="true"
Solution 3:[3]
Thanks @rahul-kavati.
For Xamarin/MAUI it is a property on ActivityAttribute
, used like this [Activity(Label = "MsalActivity", Exported = true)]
Solution 4:[4]
In Android 11 and lower, when declaring an Activity, Service, or Broadcast receiver in AndroidManifest, you did not explicitly declare android:exported. Since the default value is exported=true, you only need to declare exported=false when you do not want to disclose to the outside.
<activity android:name="com.example.app.backgroundService">
<intent-filter>
<action android:name="com.example.app.START_BACKGROUND" />
</intent-filter>
</activity>
Android 12 Changes: Explicit declaration of exported Apps that set SDK API 31 (android 12) as Target sdk on Android 12 devices must explicitly declare exported in components such as Activity that declared intent-filter. Otherwise, the following error occurs and the installation fails.
Targeting S+ (version 10000 and above) requires that an explicit value for
android:exported be defined when intent filters are present
The application could not be installed: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED
Even for apps targeting SDK API 31, components without intent-filter can omit the exported declaration.
You must explicitly declare exported as follows:
<service android:name="com.example.app.backgroundService"
android:exported="false">
<intent-filter>
<action android:name="com.example.app.START_BACKGROUND" />
</intent-filter>
</service>
Intent-filter is one of the methods for exposing the app's component to the outside. This is because the component of my app can be executed through the resolving of the implicit intent.
On the other hand, there are many cases where it is used for the purpose of executing a component with an implicit intent only inside my app, but it is exposed to the outside because exported is not set, and this may affect the resolving of the implicit intent. .
Solution 5:[5]
In AndroidManifest.xml
<activity
android:exported="true"
android:name="com.YOU.APP.activities.MainActivity"
android:launchMode="singleTask"
android:hardwareAccelerated="true">
<intent-filter>
<action android:name="android.intent.action.SEND" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="text/plain" />
</intent-filter>
</activity>
Solution 6:[6]
If you are using any intent filter or service must it have the android:export
property
Solution 7:[7]
Yes,in AndroidManifest.xml
<activity
android:exported="true" //here it is
android:name="com.YOU.APP.activities.MainActivity"
android:launchMode="singleTask"
android:hardwareAccelerated="true">
<intent-filter>
<action android:name="android.intent.action.SEND" />
<category android:name="android.intent.category.DEFAULT" />
<data android:mimeType="text/plain" />
</intent-filter>
</activity>
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
Solution | Source |
---|---|
Solution 1 | |
Solution 2 | |
Solution 3 | Andrii |
Solution 4 | linuxias |
Solution 5 | Alex Bolotnikoff |
Solution 6 | Tyler2P |
Solution 7 | Bogdan Zagreba |