This is a bug in the Eclipse Android tools.
To fix: Right click on the project, go to Android tools -> Rename application package.
And also check AndroidManifest.xml
if it updated correctly. In my case it didn’t, and that should solve this problem.
More Related Contents:
- Android Min SDK Version vs. Target SDK Version
- How to attach javadoc or sources to jars in libs folder?
- In eclipse, unable to reference an android library project in another android project
- targetSdkVersion setting
- Eclipse compiles successfully but still gives semantic errors
- Permission is only granted to system app
- Eclipse error “ADB server didn’t ACK, failed to start daemon”
- Emulator error: This AVD’s configuration is missing a kernel file
- findFragmentById for SupportMapFragment returns null in Android Studio
- Which Android IDE is better – Android Studio or Eclipse? [closed]
- Jar mismatch! Fix your dependencies
- Error inflating class and android.support.v7.widget.CardView
- Generating Google map Release API Key
- Android Unknown Command ‘crunch’
- ‘Missing contentDescription attribute on image’ in XML
- Eclipse Android project, how to reference library within workspace?
- The import android.support.v7.app cannot be resolved
- how do you display map (Google) on a phonegap android application
- Android – copy existing project with a new name in Eclipse
- Android Eclipse NoClassDefFoundError for external .jar files
- How to check if Facebook is installed Android
- ADT blank activity created with fragment activity
- Is it possible to use proguard in debug mode?
- No repository found error in Installing ADT in eclipse Indigo
- Can’t update Eclipse ADT to 22
- Can’t find AVD or SDK manager in Eclipse
- After upgrade Android on Nexus to 4.2.2, Eclipse shows target unknown for device?
- Eclipse and Android XML layouts gives “‘default’ is not a best match for any device/locale combination”
- Implementing admob for different activities
- How to take emulator screenshots using Eclipse?