19

I have a simple app HelloWorld Android app in Eclipse (Mac OS X), when I install to the emulator/AVD the app shows up in "Settings->[Devices] Apps" but not in the launcher. I notice in logcat that I get these errors

W/ActivityManager(  160): No content provider found for permission revoke: file:///data/local/tmp/HelloWorld.apk
W/ActivityManager(  160): No content provider found for permission revoke: file:///data/local/tmp/HelloWorld.apk
I/PackageManager(  160): Running dexopt on: com.example.helloworld
D/dalvikvm(  870): DexOpt: load 124ms, verify+opt 459ms, 720236 bytes
I/ActivityManager(  160): Force stopping package com.example.helloworld uid=10044

I have set read/write/execute permissions on the .android directory.

Sean McCully
  • 1,122
  • 3
  • 12
  • 21
  • 2
    See http://stackoverflow.com/a/9532683/165674 http://stackoverflow.com/a/8646393/165674 http://stackoverflow.com/q/11073358/165674 – Dheeraj Vepakomma Jul 25 '12 at 18:35
  • Thanks, but I've read and tried the recommendations from that thread – Sean McCully Jul 25 '12 at 20:16
  • @Sean ThreadS, you mentioned the `.android` and `/data/local` directory permissions, what about [deleting `dalvik-cache`](http://stackoverflow.com/questions/9532653/android-4-0-3-emulator-install-fails-with-permission-revoke/9532683#9532683)? [Trying with this app](http://stackoverflow.com/questions/11073358/android-error-message-on-install-no-content-provider-found#comment14494371_11073358)? [Trying another device](http://stackoverflow.com/a/11074769/85950)? Do those all give the same error? – blahdiblah Jul 28 '12 at 00:03

9 Answers9

6

In my case I forgot to define main activity. So, I add the following code inside AndroidManifest.xml main activity.

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

That was the result for Activity definition:

<application
    android:icon="@drawable/ic_launcher"
    android:label="@string/app_name"
    android:theme="@style/AppTheme" >
    <activity android:name="RssfeedActivity">
        <intent-filter>
            <action android:name="android.intent.action.MAIN"/>
            <category android:name="android.intent.category.LAUNCHER"/>
        </intent-filter>
    </activity>
    <activity android:name="DetailActivity"></activity>        
</application>
rgrun
  • 178
  • 3
  • 14
5

I think that the problem is with the install directory permissions. /data/local needs to have write and execute rights to others in order for adb packages to install correctly.

Source

Try this, too: Android - Download App

Community
  • 1
  • 1
Ionică Bizău
  • 109,027
  • 88
  • 289
  • 474
1

I just found solution to Linux, but I not found for Windows, maybe because in Windows the directories and permissions were confused.

It's work for me: Add the user "Everyone" in folder "C://YourUser//.Android//" with full control, then restart the emulador.

Fernando JS
  • 4,267
  • 3
  • 31
  • 29
1

I had the same problem on all of my devices. My problem was from the run configuration, I didn't checked the "launch default Activity".

Shayan_Aryan
  • 2,002
  • 1
  • 29
  • 31
1

I ran into this problem building a new signed APK.

I checked the V2(Full APK signature). Installing the APK on a device did not work anymore.

My solution was to check the V1 (Jar signature) instead. This did work.

  • This doesn't really answer the question. What does 'check' mean in this context? Where are the signatures you're 'checking'? What does it mean for the solution to 'work'? – Elliot Mar 10 '17 at 12:01
  • I guess he is talking about android studio -> generate signed apk -> sign with V1 option – yerlilbilgin Jun 03 '17 at 16:34
0

https://stackoverflow.com/a/8646393/375929 - they say it's about /data/local permissions.

And here: Change /data/local Permissions is how to fix this.

Community
  • 1
  • 1
Ivan Bartsov
  • 19,664
  • 7
  • 61
  • 59
0

My Solution was to remove the android:sharedUserId-Tag in the AndroidManifest.xml...

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.my.app"
android:theme="@style/MyAppTheme"
android:versionCode="9"
android:versionName="1.2.5" android:sharedUserId="mc">

Mustey
  • 1
0

Working on Cordova and emulator,

For me the problem was that the apk size was large and AVD RAM was too small,

problem happen when install new version of the apk and it failed with the message "No content provider found for permission revoke"

any one of those fixed the problem for me:

  • uninstall the old apk manually before install the new version
  • decrease the apk size
  • increase the device RAM
user1929819
  • 363
  • 3
  • 13
0

This works for me

Check your manifest application, if it contains this line tools:replace="android:icon"

<application android:name=".activities.MyApplication" android:allowBackup="true" android:icon="@drawable/launcher_icon" android:label="@string/app_name" android:largeHeap="true" tools:replace="android:icon">

make it like this by remove this line tools:replace="android:icon"

<application android:name=".activities.MyApplication" android:allowBackup="true" android:icon="@drawable/launcher_icon" android:label="@string/app_name" android:largeHeap="true" >

Ramesh Bhupathi
  • 408
  • 7
  • 10