every one .
now I am in a project upon android system application source code with the Android v 2.1r1 : Contacts .
I have modify the source code and run it on the emulator successfully..
but i get a problem on publishing it to my android phone with the same system version because of without signing it.
how can i do if i want to publish it to my android phone after modifying it?
do i need to resign the Contacts.apk built by mm ?
can i just signing the Contacts.apk built by mm?
thx for your reading and replies !
You do exactly what the title of your post says. Re-sign the app with your own key. Google isn't about to give you theirs. So you need to create your own key and sign your app with it.
If you don't know how to do this, there are a ton of resources/tutorials/walk throughs already on-line.
I suggest starting here
As user432209 said, you will have to resign the package with your own key. It sounds like you might also be having an issue with your version of Contacts conflicting with the version on your phone. If so, you may need to change the package name.
Related
I'm attempting to upload a build of an Android app to Google Play. I created a new keystore and signed it, but I get this error "You need to use a different package name" when I try to upload it.
I suspect that what happened is that another member of my team did this already but failed to commit their keystore file to version control. The app has never been published before, it is a new app.
I need a quick fix for this -- I won't be able to reach the team member who may have done this for several days. I tried removing the build that had been uploaded, but that didn't help.
Can I delete the entire app from Google Play and start over?
Can I change the package name? I've heard that this will work, but I'm not really sure what it entails. Do I have to actually change the package name of every class in my source code?
Thanks,
Frank
You can delete the application in the following cases
- Published apps or games that haven't been installed on any devices
- Published apps or games that no users are entitled to re-install
from here
also google does not allow uploading an app with a different signature and the same package name. What you can do now is to change the entire package name and this can be done easily in Android studio
More details
https://support.google.com/googleplay/android-developer/answer/9023647
I have a an updated APK that another developer (hired 3rd party) compiled and sent my way to upload to my Google Play Developers Console to update the previous version. The issue is that he didn't change the version code before sending it to me and leaving the country for several months (without contact). I'm not able to change the manifest (as far as I know) and I get this error when I attempt to upload:
Upload failed
You need to use a different version code for your APK because you already have one with version code 1.
Any thoughts or suggestions as to the best way around this issue? I can't wait for the developer to get back in a few months as the app is only half usable at this point. I'm WAY out of my element - hence the hiring of a third party developer.
Thanks in advance!
There is a tool called apktool located here
http://ibotpeaches.github.io/Apktool/
that may be able to help you. Essentially what it does, is it decompiles the APK file, allowing you to see the files that are inside. Once you decompile the APK, you will see a file called
apktool.yml
where you can change the version code / version name. The tricky part will now be recompiling the APK back to the original state. Apktool can help with that, as long as you have the keystore file and credentials the original developer used to sign the APK with. If you need any help with the specifics of Apktool, let me know!
I guess this could be a common problem for new android developer like myself so I thought to ask it even so it is not a big deal.
I would like to have both the current published stable version of an app and the under development version on my device. Yet when I want to install both I get
Re-installation failed due to different application signatures.
You must perform a full uninstall of the application.
I understand it technically yet I was wondering how I could have an easy way around this so I can have both application on my phone. I could change the package name for the time being but I hope there is an even more straight forward way to get it done.
Thanks
UPDATE
Solution as given by "Marc Bernstein" in the following post - thx Algo for posting the link to it
How to change package name of an Android Application
There is a way to change the package name easily in Eclipse. Right click on your project, scroll down to Android Tools, and then click on Rename Application Package.
Just change package name of your published and development version Application. Changing Package name is really very simple and easy, follow that post
https://stackoverflow.com/a/9171773/185022
The "published" version should be signed using a release keystore.
The "development" version should be signed using a debug keystore.
At installation time, Android will complain that the two applications (having the same package name) have different signatures, and won't install the latest one (Re-installation failed due to different application signatures.).
To fix this (normal) behavior, change the package name of your application while developing it (ex: com.example.myapp-dev).
We develop an app for android. When we installed the app for the first time, the app works. When we do some changes on the source, we can't install the app again without deleting it from the phone.
Is there any known workaround? When we install the app the second time, the phone shows "App not installed".
Any ideas?
It sounds like you are having some kind of namespace collision. I get this sometimes when I duplicate a project. You need to preserve a unique mapping of APK signing key to package name. See the Things That Cannot Change blog post for more details about preventing package confusion.
I have an Android project that branched into three different applications, app-1, app-2 and app-3, that apply some customizations. Currently there is a lot of code duplication, making maintenance a nightmare: do the changes in one of the branches, and then merge the other two.
So we create a library project, named app-core, that factors out most of the duplicated code. So far so good.
When I launch this into an emulator where the application was already loaded (before the refactoring), I get this exception:
Re-installation failed due to different application signatures
A different signature? But I just added a line in the .classpath to link to the app-core Java project!
The main question is: are the existing users going to be bothered by this too?
And the side question: Why is it a different signature?
The digital signature is driven by a signing key that exists on the machine that signs the app. If Developer A compiles an app using the standard debug key and installs it in an emulator, then tries installing some other variation of the app -- one signed with a production key, one signed with Developer B's debug key, etc. -- in the same emulator, you will get that error.
The main question is: are the existing
users going to be bothered by this
too?
Do you have the production signing key that you used for the version of the app your existing users are using? If yes, then there should be no problem. If no, you're screwed.
Uninstall the application on the device, then run code again, it will work. It happens for me and I tried same thing, now it is working correctly.
For this problem u need to check that the correct key is used under (Window->Preferences->Android->build).
This u can check from the android.mk file of the app.
And on placing the correct key path , CLEAN and BUILD the project to avoid this error .
I have had the similar kind of issue. If you are installing it on your device then you need to uninstall the app on your device prior to install it from eclipse. It will definitely solve your problem.
Cheers