i have lost my old debug.keystore file and i generated a new one, when i build my new apk and i want to update the old one in my phone it show me "Android App Not Install. An existing package by the same name".
Can any one help me what should i do? can i modify the debug.keystore with the old sha1 ???
Can any one help me what should i do?
Uninstall the existing app.
can i modify the debug.keystore with the old sha1 ?
No.
You will not be able to publish an update on Google Play if the app is signed by a different keystore than the one first published. You'll need to change the package name, resulting in a new app on Google Play.
If the old app isn't published just go ahead and uninstall the old app to be able to install the new.
Hi I had Shared the steps, It will definitely resolve the issue regarding Unity Android App Not Installed
UnInstall Existing App
Check is you bundle identifier is same with previous build
PlayerSettings > Enable build il2cpp Armv7 and 64bit build and donot split the build
Assign the keystore and assign password
Set the player setting SDK Card to Automatic
Make Sure your previous build is assigned with same keystore
Target Api Level should be Equal or greater than previous one
Related
i have a debug mode APK which i need to convert into release Build.
the main issue is i lost source code and keyStore file of that APK.
and app is already on playstore.
so can we change Debug Build to Release Build in this case.
Usually when you lose your keys used for signing APKs or App Bundles, you can request a new one. Losing your source code. That's a bit interesting. Don't you use Git? I don't suppose you'd have non-existant version control on a "complex" project. I'm forced to assume your app isn't too complex and could be therefore created from scratch with no trouble... Take better care and make sure to use VC and backup your keys.
Yes you can reverse engineering your own app using this tool:
https://ibotpeaches.github.io/Apktool/
You have to decode your debug apk using:
apktool d debug-app.apk
And then build again the release apk:
apktool b debug-app
Then, Sign it with your own keystore.
I have a hardware product with an application that the user is not able to exit. When there is a new update, the user is able to update to the newest version within the app. We release debug-apk's, not the signed ones.
I read that Android studio automatically signs debug-apk's. I have a new version of the app that I want to release, but the old apk's signature doesn't match the new apk signature. The users are not able to uninstall the app and reinstall the new one since they can not leave the app. I am not able to go around the world manually updating everyones product.
Question: What would be the best way to uninstall the old apk and install the new one without the user having to manually uninstall and install the new apk.
Suggestions: Is there a way to find out the old apk's automatically generated signature and change the new one to match it? Or is there a way to create a service that can uninstall the old apk and install the new one?
I could just copy the debug.keystore file from the original computer where the older versions of the app were made and replace my debug.keystore file in the users\yourname.android location on my computer. Then I had to restart android studio and everything worked normally again.
You can use that debug-key for signing your new APK and release it.
And your user can update to new one.
Actually, you don't sign the new app and just build an APK with debug-key and release it.
with below code in your gradle:
signingConfigs {
debug {
storeFile file("debug.keystore")
}
}
I installed (after unzipping) android-studio-ide-135.1224218-windows, hoping to be up and running a "hello world" program by now, but the IDE won't even start because "Your Android SDK is missing, out of date or missing templates." It tells me "You can configure your SDK via Configure | Project Defaults | Project Structure | SDKs" but when I do so, I see NOTHING in the text box for Android SDK location.
I searched for "android sdk" on my computer, and found C:\Program Files (x86)\Android\android-studio\plugins\android\lib\sdk-common.jar, but when I put that or C:\Program Files (x86)\Android\android-studio\plugins\android\lib into the text box, I get NO ERROR, but then I get the same message, and when I come back to the text box, IT DOESN'T HAVE WHAT I PUT INTO IT.
If I browse for the text box location, no matter what I put in, it says "Please choose a valid SDK directory".
That's the only "android sdk" on my computer.
I JUST installed Android Studio to C:\Program Files (x86)\Android\android-studio with no errors.
I have C:\Program Files\Java\jdk1.7.0_60 as JDK location. It won't let me change it to C:\Program Files (x86)\Java\jdk1.7.0_25.
I've Googled to see if I can download an android sdk from somewhere but found nothing.
WHAT DO I DO? I can't get into the IDE to try stuff.
sdk-common.jar is not the 'sdk' that Android Studio is looking for. You must download the sdk from SDK Manager and put it in the directory C:\Program Files (x86)\Android\android-studio\sdk.
This is what the sdk should contain:
sdk\build-tools
sdk\extras
sdk\platforms
sdk\platform-tools
...
I couldn't make use of the Answers above, so I uninstalled and then brute-force deleted EVERY trace of Android EVERYTHING.
Then I downloaded and installed installer_r23-windows.exe, putting the SDK manager out there BEFORE installing the Android Studio IDE. I allowed the default path: C:\Users\Dov\AppData\Local\Android\android-sdk.
Then I downloaded and installed android-studio-bundle-135.1245622-windows.exe--NOTE: BUNDLE, NOT IDE. I used the default folder: C:\Users\Dov\AppData\Local\Android\android-studio.
And I STILL got the SAME ERROR. But at least THIS time I could go into SDK Manager, as the error message said to do.
What I found was that the CORRECT path to the JDK, which was the same path shown in the SDK Manager dialog for installing packages. So why the error?
LOOOOOOONG story short... as I tried to browse for the path, I noticed that the AppData folder WAS NOT SHOWING.
SOLUTION: TYPE THE PATH BY HAND. It worked.
I CHANGED NOTHING, except my approach.
As it happens, "The [AppData] folder is hidden by default in File Explorer, and has three hidden sub-folders: Local, LocalLow, and Roaming." See here.
I assume that was Android Studio's problem, but why typing it by hand changed all that is anybody's guess.
I guess it's not a great idea to have AppData part of the DEFAULT install path.
(BTW, I did NOT have to mess with ANY environment variables.)
=== EDIT ===
I reinstalled Studio and SDK Manager and the above did not work. What I did BOTH times was to TRY to drag the SDK Manager.EXE file into the browse dialog from an Explorer window; it didn't work either time, but I tried today and THEN found success.... So I guess this seems to be a necessary step.... I also added \ after sdk in the text box for the SDK path.... And I clicked Apply before OK.... I hate when stuff works seemingly randomly.... Just trying to save others the frustration. Maybe Google needs to address this.
I had exactly this problem. After downloading Android Studio from the developer site:
android-studio-ide-135.1538390-windows.zip
But kept getting the error: "Your Android SDK is missing, out of date or missing templates."
Wasted several hours, but eventually went to the "Installing the Stand-alone SDK Tools" page:
https://developer.android.com/sdk/installing/index.html?pkg=tools
And downloaded and installed installer_r23.0.2-windows.exe.
Then I added its location to Configure -> Project Defaults -> Project Structure
I can now create projects.
When I build with Export Signed Application Package in Eclipse, and I use the keystore I created the first time, it works.
Now I'm trying to use ANT to build the release APK (not debug), but, when I try to install the new APK on my real phone (not emulator), it trhows an existing package by the same name with a conflicting signature and I can't install.
Of course, this means that the signature is incorrect, or something simialar with the password.
This is the info I put in local.propeties
sdk.dir=D:\\Documents\\Applications\\Android SDK
key.store=D:\\Projects\\myProject\\signature_key
key.alias=two words
key.store.password=PasswordUsing$and%
key.alias.password=PasswordUsing$and%
Yes. The key.alias has 2 words (my mistake, but it's late now)
1) Is the format valid? Should I use quotes for the alias? Should I escape $ or % characters in the password?
2) What format should I use in local.properties to make the keystore/password be valid?
3) Is there something I'm missing?
This is perfectly normal behaviour if you have previously loaded the debug version of your app on your phone. The OS recognises the package as being already present and refuses to install the release version which has been signed with a different key.
You must uninstall the debug version first, then install the release one.
If you are wanting to deploy your app to the Play Store, you will need to create your own keystore (not re-use the debug keystore the tools use to build your app by default).
Export your project using the Export Wizard (right-click on the project, Android, Export...)
When going through this Wizard, there is a selection to generate a keystore, go through that, and save the resulting keystore files (somewhere safe, if you lose these, you will NEVER be able to deploy your app again to the Play Store).
I think you should skip ANT, and instead use the Wizard GUI.
Also - keep in mind if you deploy a debug build, you will need to uninstall it, before deploying your officially signed APK.
days ago I opened ADT and it suggested to update 2-3 things. I did without even looking what they were, and after it all gen folders are empty. I have about 40 little projects, and they all don't have R and BuildConfig classes. I can't create a new project, "Compile With: " field stays empty. When I open "Android -> Properties -> Android" then everything is empty there, no Project Build Target and n o Library, and no possibility to add.
I cleaned many times, Built manually and automatically, insatlled Build Tools in SDK Manager. no error in any layout file. what else to do? Help please.
There are two parts to the tools necessary to build an Android project, the version numbers of each part need to match. I suspect that from your description, that you have only updated one, namely the Android SDK Tools
To check the version of this component, click on the Android SDK Manager icon in the toolbar and in the popped up window you will probably see "Android ADK Tools rev 22.6.2" near the top.
Now check the other necessary part, (the plugin), version number by selecting Help, Install new software, click 'what is already installed". At the top you will see the 4 plugin Android components. These need to be version 22.6.2 as well. If they are not then add the repository https://dl-ssl.google.com/android/eclipse and update it if necessary.
In Eclipse , Open Android Sdk Manager and install or update required Android SDK Build-Tools .
Then restart Eclipse .
Goto windows -> preferences -> android -> sdk location and browse your updated sdk and ok.
Hope this will solve your issue
Eclipse has Android SDK manager option Top on left side.
go to Android SDK Manager and Install Android API packages.
I had same problem yesterday and this is how I solved it :
1.Check if your SDK Manager Works if it says that tools folder is missing it means you dont have any SDK installed if you have then go to : Window -> Preferences -> Android -> and browse to find SDK in my case it is ...Documents\ADT\adt-bundle-windows-x86_64-20131030\sdk then click Apply to refresh if it found sdk chose it then do same for your project to make sure it has sdk assigned to use and about R In each class u will have to go to import section and delete R import because eclipse changed it to R.android, then just import your R. class. If that doesn't help please list more information and what you tried so far.
Good luck