CODEWITHSUNDEEP
android-studioandroid-manifest
antgel
antgel

Reputation: 1249

Android Studio gets package name wrong when running .apk

I changed my package name from com.mycompany.myapplication to com.mycompany.testapp.

Everything builds fine but when I try to run it on the emulator, I get:

The session was restarted Target device: NexusS [emulator-5554] Uploading file local path: /home/antony/AndroidStudioProjects/testappProject/testapp/build/apk/testapp-debug-unaligned.apk remote path: /data/local/tmp/com.mycompany.myapplication Installing com.mycompany.myapplication DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.mycompany.myapplication" pkg: /data/local/tmp/com.mycompany.myapplication Success

Launching application: com.mycompany.myapplication/com.mycompany.testapp.MainActivity. DEVICE SHELL COMMAND: am start -D -n "com.mycompany.myapplication/com.mycompany.testapp.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.mycompany.myapplication/com.mycompany.testapp.MainActivity } Error type 3 Error: Activity class {com.mycompany.myapplication/com.mycompany.testapp.MainActivity} does not exist.

Note the remote path ^^^ is wrong.

If I go to the emulator, I can start the app from the menu, it's just that I get this error when i try to run the app from Android Studio.

I also see in logcat, on the top-right, the drop-down offers me "No Filters" or "app:com.mycompany.myapplication". So I can't even debug properly.

Where are these references to com.mycompany.myapplication coming from, and how can I fix this?

Upvotes: 60

Views: 56595

Answers (14)

user
user

Reputation: 189

I got the same problem. None of the solutions above helped me, so I am posting another solution, which helped me.

The problem appeared after I deleted my application 'by hand' on my smartphone.

I went to settings->apps. There was my app with 'Installed not for this user' (or something similar) The solution was to delete for all users in apps' settings. (This was not done when I had deleted the app using main menu)

Upvotes: 2

Gabriel Yassunaga
Gabriel Yassunaga

Reputation: 11

None of this solutions above worked for me, but this did:

Refactor the package's name like:

com.name.examplename

Change to:

com.name.examplename2

Change your application ID with the new name of the package:

applicationId "com.name.examplename2"

Finally, go to:

File > Invalidate Caches / Restart

Wait for android studio to restart, run your application again and get happy!

Upvotes: 1

Somesh Bhalsing
Somesh Bhalsing

Reputation: 152

  1. Build APK.
  2. Transfer it to device.
  3. Install it.
  4. Now you can install the same application using ADB.

Upvotes: 0

Jonas Borggren
Jonas Borggren

Reputation: 2656

Here is how I solved it. Very simple.

Click the 'Sync Project with Gradle Files' button at the top of the window.

'Sync Project with Gradle Files' button screenshot

Look for this button if you're using newer version of Android Studio:

'Sync Project with Gradle Files' button in newer AS screenshiot

'Sync Project with Gradle Files' button in latest AS screenshiot

Upvotes: 85

For Guru
For Guru

Reputation: 1197

I Did all mentioned things but no effect. Then I found something in build.gradle file and changed it as per my new package. It worked for me.

    defaultConfig {
    applicationId "com.*****.newPackageId"
    minSdkVersion 11
    targetSdkVersion 20
}

Upvotes: 30

Brian Gaucher
Brian Gaucher

Reputation: 3

I had the exact same problem.

  • Check the manifest first of all.
  • Then Check your gradle files
  • And finally, it might be worth checking the 'test' and 'androidTest' java files.

If you don't know what to do to these files, then look at the more complete answers above.

Upvotes: 0

rsc
rsc

Reputation: 10669

Tried deleting taskArtifacts folder, invalidating,... nothing worked.

What end up working for me as forcing a Gradle Sync solved for me. (Just added a empty new line in the build.gradle to make it ask me to Sync and after the Sync it worked).

Upvotes: 0

Jack Fan
Jack Fan

Reputation: 2221

I tried to restart Android Studio but the problem still existed.

Then the solution works with me.

  1. Remove the directory ~/.gradle/caches/. It's OK to do this while Android Studio is opened. (Refer pm installing wrong package name)
  2. Press "Sync project with Gradle files" icon on Android Studio
  3. Run the project and the remote path will be correct.

Upvotes: 99

Ajji
Ajji

Reputation: 3086

If your App is getting the Same name as your MainActivity and you have tried eve, try to remove

android:label="MyMainActivity"

tag from Mainactivity, then run your app. That worked for me :)

Upvotes: 1

aggregate1166877
aggregate1166877

Reputation: 3150

My issue was that some of my .xml files (particularly AndroidManifest.xml) had their headers changed somehow.

Problematic header:

<?xml code="1.0" encoding="utf-8"?>

Change this to:

<?xml version="1.0" encoding="utf-8"?>

Notice how the problematic header shows code="1.0" instead of version="1.0".

Upvotes: 0

Mukesh
Mukesh

Reputation: 303

Clearing the cache and restart worked for me.

Go to Android Studio's File menu and select Invalidate Caches / Restart... option

Upvotes: 5

Will Yan
Will Yan

Reputation: 43

In new version of AndroidStudio, such as 0.9.1, this solution works with me:

1) remove ~/.greadle/2.1/taskArtifacts
2) clean project
3) run the project

Upvotes: 2

Boy
Boy

Reputation: 7487

What I finally did, is change the 'application ID' in the build.gradle, build and launch. Then remove the apps from the phone and revert the application ID back

Upvotes: 1

antgel
antgel

Reputation: 1249

I'll answer, just in case anyone else gets stuck with this. Strangely enough, restarting Android Studio solved the problem. Nothing more complicated, nothing less obvious.

Upvotes: 13

Related Questions