145

I am developing a small application that lists all the applications present/ installed on the android device. But I'm getting the below error while i'm trying to run the code.

Installation error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED

Please can any one help me to sort out this error.

10
  • 1
    There are many errors in the manifest.xml file that can cause this error code, see PackageParser.java error list answer below. Commented Sep 3, 2014 at 13:54
  • 1
    You didn't accept an answer? Commented Dec 16, 2014 at 13:26
  • Follow this link You will get your answer stackoverflow.com/questions/16015033/… Commented Dec 17, 2014 at 7:29
  • Check this link for a clear answer Commented Mar 24, 2015 at 16:47
  • 2
    The reason is reported in Logcat stackoverflow.com/a/24750245/1916449 Commented Jun 24, 2021 at 17:55

51 Answers 51

96

There could be another reason for this error. The attribute

android:taskAffinity="string" 

Should always start with a dot, like:

android:taskAffinity=".string" 
Sign up to request clarification or add additional context in comments.

2 Comments

Problem solved for me but, where can I find this information in documentation? there is nothing about a DOT here: developer.android.com/guide/topics/manifest/…
technically, taskAffinity doesn't have to start with dot, just containing is okay.
70

Activity name should be prefixed with "." in your manifest file.

1 Comment

in Manifest you declared package attribute with package, so when you create activity you put "." to be preceded by package name, you can also type the full name of the activity like : "com.example.test.Activity_Name", or ".Activity_Name"
58

In Android 12 or Android S [You can check to make targetSdkVersion "S" to targetSdkVersion 30 it will work fine]. For this, to work we need to update all of our dependencies to the latest one and have to add -

android:exported="true"

to to any activity, activity-alias, service, or receiver components that have intent-filters declared in the app’s AndroidManifest.xml file. Because there are few behaviors changed in Android 12.

Comments

52

The INSTALL_PARSE_FAILED_MANIFEST_MALFORMED error code is returned by PackageParser.java when it detects any of a large number of errors in the manifest.xml file.

To isolate the error, look in logcat (when you do the 'adb install foo.apk' command). In the problem I encountered, logcat contained:

W/ActivityManager(  360): No content provider found for permission revoke: file:///data/local/tmp/foo.apk
D/Finsky  (32707): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 6
D/Finsky  (32707): [1] WorkerTask.onPreExecute: Verification Requested for id = 6,   data=file:///data/local/tmp/foo.apk flags=112 fromVerificationActivity=false
W/PackageParser(32707): /data/local/tmp/foo.apk (at Binary XML file line #214): <provider> does not include authorities attribute
D/Finsky  (32707): [716] PackageVerificationService.getPackageInfo: Cannot read archive for file:///data/local/tmp/foo.apk in request id=6
D/Finsky  (32707): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 6
W/ActivityManager(  360): No content provider found for permission revoke: file:///data/local/tmp/foo.apk
I/PackageManager(  360): Copying native libraries to /data/app-lib/vmdl1205566381
W/PackageParser(  360): /data/app/vmdl1205566381.tmp (at Binary XML file line #214): <provider> does not include authorities attribute

In the fourth line above, you can see that PackageParser complains that line #214 of the manifest.xml file "<provider> does not include authorities attribute". See the listing below of all the cases in PackageParser that returns that error code. (PackageParser is the only class that produces the PackageManager.INSTALL_PARSE_FAILED_MANIFEST_MALFORMED error code)

In my case the message "<provider> does not include authorities attribute" is produced by line 2490 of PackagerParser.java in the parseProvider function called by parseApplication.


From the 4.1.1 version of frameworks/base/core/java/android/content/pm/PackageParser.java, PackageManager.INSTALL_PARSE_FAILED_MANIFEST_MALFORMED is referenced on these lines in these methods. If the source code line number is followed by a quoted string that is the message printed in logcat. if the line number is followed by a Java expression that is the code that caused that error code to be returned that that function should be investigated to see what caused the error message to be returned. In a couple cases I couldn't isolate the error cause to one specific method call.

in parsePackage:
  536:  (only used in 'core apps' with no 'pkg')
  973:  "<manifest> has more than one <application>"
  1275: "Bad element under <manifest>: "      --if RIGID_PARSER

in parsePermissionGroup:
  1464: !parsePackageItemInfo(owner, perm.info, outError,
    "<permission-group>", sa,
    com.android.internal.R.styleable.AndroidManifestPermissionGroup_name,
    com.android.internal.R.styleable.AndroidManifestPermissionGroup_label,
    com.android.internal.R.styleable.AndroidManifestPermissionGroup_icon,
    com.android.internal.R.styleable.AndroidManifestPermissionGroup_logo)
  1482: !parseAllMetaData(res, parser, attrs, "<permission-group>", perm,
    outError)

in parsePermission:
  1506: !parsePackageItemInfo(owner, perm.info, outError,
    "<permission>", sa,
    com.android.internal.R.styleable.AndroidManifestPermission_name,
    com.android.internal.R.styleable.AndroidManifestPermission_label,
    com.android.internal.R.styleable.AndroidManifestPermission_icon,
    com.android.internal.R.styleable.AndroidManifestPermission_logo)
  1530: "<permission> does not specify protectionLevel"
  1541: "<permission>  protectionLevel specifies a flag but is not based on signature type"
  1548: !parseAllMetaData(res, parser, attrs, "<permission>", perm, outError)

in parsePersmissionTree:
  1572: !parsePackageItemInfo(owner, perm.info, outError,
    "<permission-tree>", sa,
    com.android.internal.R.styleable.AndroidManifestPermissionTree_name,
    com.android.internal.R.styleable.AndroidManifestPermissionTree_label,
    com.android.internal.R.styleable.AndroidManifestPermissionTree_icon,
    com.android.internal.R.styleable.AndroidManifestPermissionTree_logo)
  1585: "<permission-tree> name has less than three segments: "+perm.info.name
  1595: !parseAllMetaData(res, parser, attrs, "<permission-tree>", perm, outError)

in parseInstrumentation:
  1625: new Instrumentation(mParseInstrumentationArgs, new InstrumentationInfo())
  1648: "<instrumentation> does not specify targetPackage"
  1654: !parseAllMetaData(res, parser, attrs, "<instrumentation>", a, outError)

in parseApplication:
  1678: buildClassName(pkgName, name, outError) == null
  1851: (Set by various other functions)
  1869: parseActivity(owner, res, parser, attrs, flags, outError, false, hardwareAccelerated) == null
  1878: parseActivity(owner, res, parser, attrs, flags, outError, true, false) == null
  1887: parseService(owner, res, parser, attrs, flags, outError) == null
  1896: parseProvider(owner, res, parser, attrs, flags, outError) == null
    2484: "Heavy-weight applications can not have providers in main process"
    2890: "<provider> does not incude authorities attribute"
  1905: parseActivityAlias(owner, res, parser, attrs, flags, outError) == null
  1917: parseMetaData(res, parser, attrs, owner.mAppMetaData, outError) == null
  1969: "Bad element under <application>: "+tagName

It's regrettable that you have to poke around in logcat and the source to figure out what causes a problem.

5 Comments

thanks for helping us understand how to solve the general problem in addition to giving a specific solution.
There are multiple reason, for this exception. This is most logical answer.
Thank you - in my case I had a IntentFilter.MalformedMimeTypeException that I missed.
This is the correct answer by far. How useful is logcat?
In my case, an old dependency on LeakCanary and exported being false within it was causing the issue
48

I was having this error because i had capital letters in my package name like this

Com.Example.packagename

after i had changed it to something like

com.example.packagename

it was solved

2 Comments

this solved my problem. My activity class was under a package which called Activities, and i add it to manifest before this error appeared. when i changed the Activities package name to activities, it solved. Thanks
I think you can have capital letters in the package name, however, the 1st letter in the package name cannot be a capital letter. So "myActivity" = OK but "MyActivity"= Not OK
29

Add

android:exported="true"

to your activity in Manifest.xml

Like this;

<activity
    android:name=".MainActivity"
    android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
</activity>

2 Comments

Can you explain why?
Here you can find the explanation: developer.android.com/guide/topics/manifest/…
9

Check your Activity name in manifest file

or the Package name in main activity/class

<activity android:name="MainActivity"></activity>

Comments

9

I have the same issue but when i call process like this:

<service
    android:name="com.dexode.tama.AppService"
    android:process="screen" >
</service>

When i change to:

<service
    android:name="com.dexode.tama.AppService"
    android:process=":screen" >
</service>

Everything starts working.

1 Comment

By adding the ':' you changed the semantics of the code. In the second case the application will create a new process for the service which is available to that application only. developer.android.com/guide/topics/manifest/…. Instead the error can be fixed by mentioning the complete package name instead of just the word 'screen'.
9

I ran into the same problem time ago, in the android docs they said that if you don't use ":" as prefix in android:process you should use a lower case letter, but they never said that, then it should be a package like process name, like com.company.app.services.MyService

1 Comment

Even I had the same problem. They should have mentioned the we need to include package name for when not using ':'
7

Any name such as android:name, android:process should be in form of package name: starts with a..z, combines with others with ., do not end with ....

2 Comments

@IgorG. Sorry I lost my point :-( But the new SDK removed that field (here).
Thank you. I called a process such a way: android:process="com.my_pack.services.MyServiceProcess" (com.my_pack.services is the package where my service is) and the installation error will not show up after that.
7

My issue was that I had written (Notice the - vs. the _):

<meta_data ... /> 
<!-- instead of -->
<meta-data ... />

under an activity. This might be the cause of your issue as well.

Comments

6

Read your Android device logs to diagnose this error. Expect a "W/PackageParser" line explaining the problem.

Comments

5

In my case I was referring to an icon using an attribute like this:

<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="?attr/ic_notify" />

instead of the drawable:

<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/ic_notify" />

I am using this attribute in several places but it seems it does not work in manifest.

1 Comment

Exactly my case. I need it to be a different color depending on user's preferences. Sadly, android:resource doesn't accept attributes...
5

I had this error because of the code below:

<intent-filter>
     <action android:name="android.intent.action.VIEW" />
     <category android:name="android.intent.category.DEFAULT" />
     <data android:mimeType="*" android:host="*" android:scheme="content" />
</intent-filter>

When I changed android:mimeType="*" to android:mimeType="*/*", it fixed the error.

Comments

5
        <activity android:name=".MainActivity"
        android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>

            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
    </activity>

if you're using target API 31+ you have to add exported with true

Comments

3

Got the same error! had empty permission tag and that was causing the problem!

1 Comment

Please add some more detail to your answer
3

I run into the same problem after adding localizations

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="my.package"
    android:versionCode="10"
    android:versionName="@string/version_name" >

The string @string/version_name accidentally passed into one of new added localized string-file (it appeared only in the new files). After checking all the localizations and removing @string/version_name from every file except eng locale everything worked again

Comments

3
<activity/>

must be defined BEFORE

<activity-alias/>

1 Comment

I wish I could upvote this again. Second time this answer has helped me
3

activity created name folder must be small letters, Dont use capital letters for activity folder name.... its always better to use small letters.

Comments

3

this can be for many reasons , but for me it was solved by changing the name of package with lowercase name (package name was Activities , solved with activities) .

Comments

3

[Solution] 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>

Comments

2

If you are using multidex in manifest then it should be added with value or resource. Like..

<meta-data android:name="android.support.multidex.MultiDexApplication"
android:value="@string/yourValue" />

OR

<meta-data android:name="android.support.multidex.MultiDexApplication"
android:resource="@string/yourValue" />

then clean the project and reinstall the app.

Comments

2

I create a new application and target it to Android Pie. Everything was working well and good then lately I found that my application don't installs to Android Naught and below version of Android OS.

While installing, I see failure message

Installation failed with message INSTALL_PARSE_FAILED_MANIFEST_MALFORMED.

So what fixes which I made are as follow and they all need to be done in AndroidManifest.xml file only.

For activity, service, receiver and all

Instead of:
    android:name=".service.MyService"

Used: 
    android:name="com.complete.appicationID.service.MyService"

For Manifest permissions

Instead of: 
     <uses-permission android:name="{applicationId}.permission.MAPS_RECEIVE" />
     <permission
         android:name="{applicationId}.permission.MAPS_RECEIVE"
         android:protectionLevel="signature" />

Used:
     <uses-permission android:name="com.complete.appicationID.permission.MAPS_RECEIVE" />
     <permission
         android:name="com.complete.appicationID.permission.MAPS_RECEIVE"
         android:protectionLevel="signature" />

That were all changes which I had to perform to make it work for lower version devices as well.

1 Comment

In Xamarin android fixed on Activity Name attribute. That's work for me
2

Target <activity> needs to be specified before the <activity-alias>.

Comments

2

if you're using target api 31 or 32 in Android 12 or Android S so you'd face this error to solve this

Add this line to the laucher activity in Manifest

android:exported="true"

This element sets whether the activity can be launched by components of other applications:

  • If "true", the activity is accessible to any app, and is launchable by its exact class name.
  • If "false", the activity can be launched only by components of the same application, applications with the same user ID, or privileged system components. This is the default value when there are no intent filters.

Whether or not hardware-accelerated rendering should be enabled for this Activity — "true" if it should be enabled, and "false" if not. The default value is "false".

<activity
    android:name=".MainActivity"
    android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
</activity>

Comments

2

I had same issue on Android 12 and fixed it this:

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 attribute for these app components. If the app component includes the LAUNCHER category, set android:exported to true. In most other cases, set android:exported to false.

Also I updated third party Dependencies.

Comments

2

If you have AndroidStudio 4.1.2 try to add : android:exported="true" & android.name=".MainActivity" in the file "AndroidManifest.xml"

platform/android/AndroidManifest.xml

Your application & activity should seen be this way:

<application .....
  <activity android:exported="true" android:name=".MainActivity" 

Comments

2

The Problem

This INSTALL_PARSE_FAILED_MANIFEST_MALFORMED error only indicates there is an error within your manifest (or one of the manifests in your project & dependencies) that manifested (pun intended) itself when the app was pushed to an emulator or device for installation.

Installation failed due to: 'INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: 

These runtime errors won't block compilation of the the project within Android Studio so at first view you get a Build Success and everything seems fine.

Finding the actual root source

Best solution is to start by making sure you have the latest build tools. That will increase the likelihood of having a proper error detail message like the one listed below. You can find this by opening the Run tab at the bottom in Android Studio to see the outcome of the installation adb commands.

Installation failed due to: 'INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: Failed parse during installPackageLI: /data/app/vmdl1428212790.tmp/base.apk (at Binary XML file line #96): be.hcpl.android.phototools.links.AddLinkActivity: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'

With all default settings this window should open after running the app. If not this is where to find it (also on a default layout that is).

android studio run tab

I've pasted the full error message here also so you can clearly see that in my case the detail message clearly indicates what the issue in the manifest is. Here; a missing export tag on the AddLinkActivity activity declaration.

Alternative Approach

If, for whatever reason, that detail message is missing or not clear enough to point to the root cause an alternative approach is to open the AndroidManifest.xml file in your project and then open the Problems tab.

enter image description here

This view is a list of all the errors and warnings found on that specific file, when Current File is selected.

In the file itself you can also see that the Activity declaration is marked in the editor. Including a quick fix tooltip to add the missing export tag.

Comments

1

There could be other files that are malformed but aren't highlighted in the IDE, for example the res/values/strings which the manifest may reference for things like labels.

Comments

1

In my case the cause was absence of android:name attribute in < activity-alias >. It is obligatory for < activity-alias > although it must not name an existing class. Funny thing is - the project compiles without problems.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.