Issue: You uploaded an APK or Android App Bundle which has an activity, activity alias, service, or broadcast receiver with intent filter, but without the 'android: exported' property set. This file can't be installed on Android 12 or higher. See developer.android.com/about/versions/12/behavior-changes-12#exported
My AndroidManifest.xml file
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.c4life.guardianangel">
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION"/>
<application
tools:replace="android:label"
android:label="GA"
android:exported="true"
android:icon="#mipmap/ic_launcher">
<meta-data android:name="com.google.android.geo.API_KEY"
android:value="[insert API key here]"/>
<activity
android:name=".MainActivity"
android:exported="true"
android:launchMode="singleTop"
android:theme="#style/LaunchTheme"
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
android:hardwareAccelerated="true"
android:windowSoftInputMode="adjustResize">
<meta-data
android:name="io.flutter.embedding.android.NormalTheme"
android:resource="#style/NormalTheme"
/>
<meta-data
android:name="io.flutter.embedding.android.SplashScreenDrawable"
android:resource="#drawable/launch_background"
/>
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>
<service android:name="changjoopark.com.flutter_foreground_plugin.FlutterForegroundService" android:exported="false"/>
<meta-data
android:name="flutterEmbedding"
android:value="2" />
</application>
<uses-sdk
android:targetSdkVersion="30"
tools:overrideLibrary="changjoopark.com.flutter_foreground_plugin" />
According to google new policy If your app targets Android 12 or higher and contains activities, services, or broadcast receivers that use intent filters, you must explicitly declare the android:exported: true attribute for these app components.
FOR FLUTTER AND REACT NATIVE PROJECTS :
add this line to AndroidManifest.xml file of project :
android:exported="true"
Now just rebuild your project. In most of the cases this work like a charm.
If above solution is not working or if your project is in Android Native follow the below instructions :
In the main manifest file check all the activities, services, and receivers that can use intent-filter which are without the android: exported tag.
Add android:exported="true" or android:exported="false" for these tags.
You might ask when I need to add android:exported="true" or android:exported="false" to the activities, services, or broadcast receivers that use intent filters. If the app component includes the LAUNCHER category, set android: exported to true otherwise set android: exported to false.
If adding the android: exported in the main manifest file not works for you follow the below steps:
open AndroidManifest.xml file and at the bottom select Merged Manifest.
like this :
if you are not able to preview Merged Manifest then in your build.gradle file
set compileSdkVersion 30 and targetSdkVersion 30 and sync your project and now try to open the merged manifest again I hope this time you will have a proper preview of the merged manifest. but if there is no preview don't worry you can still navigate to individual manifest files from different third-party libraries you have used in your project.
Note: also check individual third-party library manifest files if there is any activity, service, or receiver using then you have to override the same activity, service, or receiver in your main manifest file with android: exported property.
For Example in my case I have defined android: exported for each and every activity, service, or receiver in my main manifest file but in my project, I was using Razorpay dependency so in the manifest of Razorpay I found that there is an activity and receiver which are using property without android: exported so I declared them in my main manifest files.
as shown below :
<activity
android:name="com.razorpay.CheckoutActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
android:theme="#style/CheckoutTheme"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<data
android:host="rzp.io"
android:scheme="io.rzp" />
</intent-filter>
</activity>
<receiver android:name="com.razorpay.RzpTokenReceiver"
android:exported="true"
android:permission="android.permission.INTERNET">
<intent-filter>
<action android:name="rzp.device_token.share" />
</intent-filter>
</receiver>
Note: in your case, you may have to go through more files and check activity, and services, and mention them in your main manifest file.
also after doing all this you can change back to targetSdkVersion 31 and compileSdkVersion 31 in your build.gradle file.
In my case, I just add this line to my manifest:
android:exported="true"
I finally fixed this issue
1: install emulator with android v 12
2: run your app
the compailer will tell you what service/reciver...etc casued the issue
now you have to add it to your manifist and add the android:exported="true" to it
in my case the prblem was with the local notifcation package
i got the message to fix this receiver
com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver
so i added to my manifist out side the main activity
<receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED"/>
<action android:name="android.intent.action.MY_PACKAGE_REPLACED"/>
</intent-filter>
</receiver>
and it worked as intended
By just adding exported:true to your Android manifest activity did not solve my issue. Probably because the libraries your application depends on does not have exported:true You shouldn't encounter this bug in the future as long as the libraries are updated with exported:true
You have to
open project in Android studio
Open Androidmanifest.xml
At the bottom select merged manifest
Now ensure that you add exported to true wherever stated and fix those warnings specified on the line (in blue) and tapping blue text does not take you to one of these tags Services, activity, receiver in above step then look for the library for which the merge error exist
e.g a merge error here shows issue in flutter.plugins.firebasemessaging.FlutterFirebaseMessagingService
So go to the manifest of that specific library which is listed in blue above the error, where you can add exported to true.(this will also resolve the merge error)
Add exported to true in services tag
Video demo here: https://www.youtube.com/watch?v=hy0J8MNnE6g
if use targetSdkVersion=31
package="com.name.app"><!-- Channnge your package -->
<queries>
<intent>
<action android:name="android.intent.action.VIEW" />
<data android:scheme="https" />
</intent>
<intent>
<action android:name="android.intent.action.DIAL" />
<data android:scheme="tel" />
</intent>
<intent>
<action android:name="android.intent.action.SEND" />
<data android:mimeType="*/*" />
</intent>
</queries>
<application
android:label="Tut Elimi"
android:icon="#mipmap/ic_launcher">
<service android:name="com.example.app.backgroundService"
android:exported="true">
<intent-filter>
<action android:name="com.example.app.START_BACKGROUND" />
</intent-filter>
</service>
<meta-data
android:name="com.google.android.gms.ads.APPLICATION_ID"
android:value=""/>
<activity
android:name=".MainActivity"
android:launchMode="singleTop"
android:theme="#style/LaunchTheme"
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
android:hardwareAccelerated="true"
android:windowSoftInputMode="adjustResize"
android:exported="true">
<!-- Specifies an Android theme to apply to this Activity as soon as
the Android process has started. This theme is visible to the user
while the Flutter UI initializes. After that, this theme continues
to determine the Window background behind the Flutter UI. -->
<meta-data
android:name="io.flutter.embedding.android.NormalTheme"
android:resource="#style/NormalTheme"
/>
<meta-data
android:name="io.flutter.embedding.android.SplashScreenDrawable"
android:resource="#drawable/splash"
/>
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action android:name="FLUTTER_NOTIFICATION_CLICK" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
<!-- Displays an Android View that continues showing the launch screen
Drawable until Flutter paints its first frame, then this splash
screen fades out. A splash screen is useful to avoid any visual
gap between the end of Android's launch screen and the painting of
Flutter's first frame. -->
</activity>
<!-- Don't delete the meta-data below.
This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
<receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED"/>
<action android:name="android.intent.action.MY_PACKAGE_REPLACED"/>
</intent-filter>
</receiver>
<service
android:name="com.name.app.BackgroundService"
android:enabled="true"
android:exported="true" />
<meta-data
android:name="flutterEmbedding"
android:value="2" />
</application>
</manifest> ````
The "exported" attribute describes whether or not someone else can be
allowed to use it.
So if you have "exported=false" on an Activity, no other app, or even
the Android system itself, can launch it. Only you can do that, from
inside your own application.
So settings "exported=false" on the Activity marked as the LAUNCHER
Activity would basically tell the system that it cant launch your
application, ever.
If you are not using any other project then update all library latest versions because some old library AndroidManifest.xml not added android: exported in activities, services, or broadcast receivers
If your Android Studio don't show the Merged Manifest tab, you can figure out what is the problem by searching on the merged AndroidManifest.xml file.
To me it was on: \build\app\intermediates\merged_manifests\release\AndroidManifest.xml
And my problem was the ScheduledNotificationBootReceiver:
Add this to your Manifest:
<receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver"
android:exported="true">
</receiver>
If you are flutter developer and unable to find Merged Manifest tab, follow th e steps:
Open Project in Android Studio.
Navigate to main AndroidManifest.xml.
Navigation
Wait for Project Loading
Wait for Project
Here it is... Found
The problem on my RN app is that at debug/AndroidManifest.xml the exported for facebook.react.devsupport was set to false. changed that to true solved it.
Pressing merged Manifest showed me where the issue is.
Hope that helps.
Xamarin Forms: I was able to publish it, I had to update the AndroidManifest with the path obj\Release\120\android\manifest since some "receiver" were not there and had not added the "android:exported".
This is for Unity Developers in specific and for any frame work targeting android platform in general. If by any means, you are not able to publish even if you have added android:exported property to every activity/receiver containing intent filter, then you should do this approach and hopefully you will be able to solve the issue.
Problem
Recently, Playstore started to require apps / games to target API 31. You updated SDK, Gradle and all that stuff. You got a build, published to PlayStore and now Playstore is telling you, this
you uploaded an APK or Android App Bundle which has an activity, activity alias, service or broadcast receiver with intent filter, but without 'android:exported' property set.
YOU HAVE ALREADY TRIED
You now know that the Android Manifests including in you app / game contains some Activities, receivers, activity-alias etc which contain intent-filter but does not have android:exported property set to true or false.
You tried adding this property to all of the Manifests and unity 's own manifest by Enablisng Custom Android Manifest too. But still Playstore is not accepting the app.
You don't want to update Unity version to fix this. You still have a solution.
Let's Narrows down
You are doing good in adding android:exported property but when you are getting build, not all of those tags persist. During build, unity is replacing you properties, especially properties related to external plugins you have used in your app.
So lets have a look which plugins contain problematic activities/receivers etc.
Instead of building a bundle or apk, Export your unity project as Android Project.
Open project in android studio, and build there.
After build is complete, go to this file which is the Merged Menifest containing data from all individual manifests.
YourExportedProjectFolder\launcher\build\intermediates\merged_manifests\release
Go precisely through this file and check which activities/receivers etc does not contain exported:property set. Not down that plugin. That is the culprit.
Let's fix it
Go back to unity, go to the relevant plugin manifest, copy those specific problematic activities (Complete i.e. along with intent-filters) from that manifest and paste to
Assets/Plugin/Android/AndroidManifest
Something like this
<receiver android:name="universal.tools.notifications.ScheduledNotificationsRestorer"
android:exported="true"
tools:replace="android:exported">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
</intent-filter>
</receiver>
Now build again and you should be good to go!
for react native that have many library i fix it with this step :
first is you build or run, then you look at app/build/intermedied/merged_manifest/release/AndroidManifest.xml
then look at all that have then copy from open tag above it and the closing tag either it activities, services, or broadcast, receivers. then paste to folder android/app/src/main/AndroidManifest.xml and dont forget to put android:exported="true" to fix it. if you already cover all intent-filter then save then build again.
For Unity i did this, i went to gameProjectFolder\Temp\StagingArea y copy unityManifest to gameProjectFolder\Assets\Plugins\Android and changed the name to
AndroidManifest and in the label activity I add android:exported="true"
Adding the line android:exported="true" to my Manifes
Need to add android:exported="true" to all components which has an intent-filter.
See where you need to add it you can opening Merged Manifest file.
Just change
build.gradle -> defaultConfig
targetSdkVersion="31"
to
targetSdkVersion="30"
work normal for me.
I have an application that I want to create an instantApp for it.
I successfully apply changes to my project and it builds successfully.
But there is 2 problem:
-I couldn't run the application and the error is:
Default Activity not found
And another problem is that when I run the instantApp I see an error message that says Google Play Store has stoped
I have an app and two Instant App Feature Module that are base and feature.
And these is my feature manifest:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools"
package="instantapp.samples.yaramobile.com.base.feature">
<application tools:ignore="GoogleAppIndexingWarning">
<activity android:name=".presenter.MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter
android:autoVerify="true"
android:order="1">
<action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.BROWSABLE"/>
<category android:name="android.intent.category.DEFAULT"/>
<data android:host="test.com"/>
<data android:pathPattern="/"/>
<data android:scheme="https"/>
<data android:scheme="http"/>
</intent-filter>
</activity>
<activity android:name=".presenter.display.DisplayActivity"/>
<activity android:name=".presenter.display.PermissionActivity"/>
</application>
</manifest>
I finally found the problems and solutions:
The problem was about AppCompact dependency:
implementation 'androidx.appcompat:appcompat:1.0.2'
there was a conflict and I had to use of api instead of implementation
api 'androidx.appcompat:appcompat:1.0.2'
and there was another conflict with room dependencies:
implementation 'androidx.lifecycle:lifecycle-extensions:2.0.0'
kapt 'androidx.lifecycle:lifecycle-compiler:2.0.0'
implementation 'androidx.room:room-runtime:2.1.0-alpha02'
kapt 'androidx.room:room-compiler:2.1.0-alpha02'
I had to replaced with api too:
api 'androidx.lifecycle:lifecycle-extensions:2.0.0'
kapt 'androidx.lifecycle:lifecycle-compiler:2.0.0'
api 'androidx.room:room-runtime:2.1.0-alpha02'
kapt 'androidx.room:room-compiler:2.1.0-alpha02'
Another problem was about databinding
I Just added databinding in my base module but it's needed in installed module too:
dataBinding{
enabled = true
}
and again is about room:
I had to add a provider into the manifest of the base module because I had an error in merge manifest in my installed module because of these provider that is used in room dependencies:
<provider
tools:replace="android:authorities"
android:name="androidx.lifecycle.ProcessLifecycleOwnerInitializer"
android:authorities="codenevisha.ir.mvvmwithdagger.base.lifecycle-process"
android:exported="false"
android:multiprocess="true"/>
don't forget to replace this provider with adding tools:replace="android:authorities"
Hope these guidelines will you too.
Based from this thread, if you see that error occur after upgrading versions of IntelliJ IDEA or Android Studio, or after Generating a new APK, you may need to refresh the IDE's cache.
File -> Invalidate Caches / Restart...
It also means that you don't have an activity declared in AndroidManifest.xml that is marked as the main activity to be launched when the application starts.
When I add
dependencies {
compile 'com.google.zxing:core:3.0.0'
}
and
dependencies {
compile files('./libs/zxing/core.jar')
}
in build.gradle in both cases it shows error in manifest file
Cannot resolve symbol 'CaptureActivity'
Manifest File is as
<activity
android:name="com.google.zxing.client.android.CaptureActivity"
android:configChanges="orientation|keyboardHidden"
android:screenOrientation="landscape"
android:theme="#android:style/Theme.NoTitleBar.Fullscreen"
android:windowSoftInputMode="stateAlwaysHidden" >
<intent-filter>
<action android:name="com.google.zxing.client.android.SCAN" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
When i add
com.google.zxing.client.android.captureactivity.jar
in libs folder then Manifest error is solved but it gives
Multiple dex files define Lcom/google/zxing/BarcodeFormat;
Is it necessary to add captureactivity.jar in libs, if not then how to solve manifest error.
The short answer is: CaptureActivity is not part of the core library, and is not meant to be used as if it is a library. It is in android/, and you can reuse parts of that code for your own app, but you should be writing your own app from scratch rather than cloning the Barcode Scanner app, which seems to be your starting point here. Please read https://github.com/zxing/zxing/wiki/License-Questions
To my Android app project, I added a module which contains an activity named "SampleDataMenuActivity". There is nothing special to this activity - it's added using the "New Module" -> "Android Library" dialog in Android Studio and includes the "Hello World" code generated by Android Studio.
The AndroidManifest.xml of the app includes (from the module):
<activity
android:name="com.sample.sampledata.SampleDataMenuActivity" >
<intent-filter>
<action android:name="android.intent.action.SampleDataMenuActivity" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
In the build.gradle of the app:
dependencies {
(...)
compile project(':sampledata')
}
In the settings.gradle of the project:
include ':sampledata', ':app'
In the main activity of my app, I want to navigate to an activity in the module using:
startActivity(new Intent("com.sample.sampledata.SampleDataMenuActivity"));
The project builds just fine, but when I tap the button that should take me to the activity in the module it fails, reporting:
android.content.ActivityNoFoundException: No Activity found to handle Intent ( act=com.sample.sampledata.SampleDataMenuActivity )
What did I miss?
I found the mistake, and perhaps I should remove the question. But as it was upvoted, somone else might be interested in this answer:
The manifest should state:
<activity
android:name="com.sample.sampledata.SampleDataMenuActivity" >
<intent-filter>
<action android:name="com.sample.sampledata.SampleDataMenuActivity" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
I have
Single main project which defines <action android:name="android.intent.action.MAIN" /> and <category android:name="android.intent.category.LAUNCHER" />
Multiple library projects, with some of them defines <action android:name="android.intent.action.MAIN" /> and <category android:name="android.intent.category.LAUNCHER" />
While I'm using Eclipse to build & run single main project with multiple library projects, only 1 app will be installed.
However, if I migrate to Android Studio to build & run single main project with multiple library projects, multiple apps will be installed,
depending on how many projects (regardless main project or library projects) define <action android:name="android.intent.action.MAIN" /> and <category android:name="android.intent.category.LAUNCHER" />
I was wondering, is there any configuration I had done wrong in Android Studio, which causes multiple app to be installed, when I build & run the projects?
Currently, my only workaround is to remove those lines (<action android:name="android.intent.action.MAIN" /> and <category android:name="android.intent.category.LAUNCHER" />) from all library projects' AndroidManifest.xml. Is that common & correct way, to import project libraries in Android Studio? As in Eclipse, those lines don't install extra apps into my device.
This is how my Project Structure looks like
As you can see the first folder icon, looks different than rest of the folder icons. I guess that indicate, the first folder icon is main project, the others are library projects.
If there is only 1 main project, how come there can be multiple apps being installed?
In Eclipse only the AndroidManifest.xml from main app project is used. In Android Studio (and Gradle build system) all the manifests are merged together.
The following lines inside an <activity> element in your manifest indicate that that activity should be shown in the launcher menu. If you do not wish this, remove those lines.
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
All of this is intended behavior.
There's another hackish way.
Look up at your merged AndroidManifest.xml. It should be located at:
<your_project>/build/intermediates/manifests/full/<debugOrRelease>/AndroidManifest.xml
Search for the LAUNCHER <activity> tag. In your case you should have more than 1 LAUNCHER <activity> tags. My case looks like this:
<activity
android:name="com.stockhut.SplashScreenActivity"
android:screenOrientation="portrait" >
<intent-filter>
<action android:name="android.intent.action.MAIN" >
</action>
<category android:name="android.intent.category.LAUNCHER" >
</category>
</intent-filter>
</activity>
...
<activity
android:name="com.todddavies.components.progressbar.main"
android:label="#string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
In my case, com.todddavies.components.progressbar.main is a library project with a sample project that has been declared as LAUNCHER. The correct LAUNCHER should be com.stockhut.SplashScreenActivity.
Open AndroidManifest.xml in your main project, add the following:
<activity
android:name="com.todddavies.components.progressbar.main"
android:label="#string/app_name" tools:node="remove" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
Take note on the Marker tools:node="remove". According to Android Manifest Merger Documentation:
A marker is a special attribute, in the tools namespace, used to express a specific decision for how to resolve conflicts.
Therefore an <activity> tag with the marker tools:node="remove" will tell Gradle to remove itself when there's a conflict. In other words, we are somehow "forcing a conflict". It is a little hackish, but it works.
You can always verify your merged AndroidManifest.xml in the abovementioned path.
In Android studio their can be only one project at a time that can be added.
If you have library with project then you have to either add whole code inside you project or
you can create jar for your library project and add them into your project.
There is another option of gradle in Android studio.
If we want to use any library in project we can add their dependency in "build.gradle" file of Project.
I am attaching a screen shot of "build.gradle" file please refer to it.
Now , As far as Library Projects are concerned , (if it is not contributing to your project) The Best Approach is that in Android manifest you should set only your defined activity as a launcher activity ,As In Most cases libraries AndroidManifest.xml Often contain some sample Activity (which should be removed), or Activity which you need to subclass , There should be minimal defined things in the library project (negligible) most of the things should be in your Manifest including all permission.
Also it is define on android developer site
"a filter with "android.intent.action.MAIN" and
"android.intent.category.LAUNCHER" settings advertises an activity as
one that initiates an application — that is, as one that should be
displayed in the application launcher. The icon and label set in the
filter are therefore the ones displayed in the launcher."
you can refer the link also...
http://developer.android.com/guide/topics/manifest/manifest-intro.html