I originally saw this error after upgrading from 0.2.13 to 0.3. These instructions have been updated for the release of Android Studio 0.5.2. These are the steps I completed to resolve the issue. 1.In build.gradle make sure gradle is set to 0.9.0 buildscript { repositories { mavenCentral() } dependencies { classpath ‘com.android.tools.build:gradle:0.9.0’ } } 2.In … Read more
First, an apk file is just a modified jar file. So the real question is can they decompile the dex files inside. The answer is sort of. There are already disassemblers, such as dedexer and smali. You can expect these to only get better, and theoretically it should eventually be possible to decompile to actual … Read more
This error may be caused by several reasons. Here is the list of requirements for the Google IAB testing. Prerequisites: AndroidManifest must include “com.android.vending.BILLING” permission. APK is built in release mode. APK is signed with the release certificate(s). (Important: with “App Signing by Google Play” it only works if you download directly from GooglePlayStore!) APK … Read more
I found that this error can now also occur when using the wrong signing config. As described here, Android 7.0 introduces a new signature scheme, V2. The V2 scheme signs the entire APK rather than just the JAR, as is done in the V1 scheme. If you sign with only V2, and attempt to install … Read more
None of these suggestions worked for me, because Android was appending a sequence number to the package name to produce the final APK file name. On more recent versions of Android (Oreo and Pie), an unpredictable random string is appended. The following sequence of commands is what worked for me on a non-rooted device: 1) … Read more
The manual is clear enough. Please specify what part you get stuck with after you work through it, I’d suggest: https://developer.android.com/studio/publish/app-signing.html Okay, a small overview without reference or eclipse around, so leave some space for errors, but it works like this Open your project in eclipse Press right-mouse – > tools (android tools?) – > … Read more
You can access the APK’s signing signature like this using the PackageManager class http://developer.android.com/reference/android/content/pm/PackageManager.html Signature[] sigs = context.getPackageManager().getPackageInfo(context.getPackageName(), PackageManager.GET_SIGNATURES).signatures; for (Signature sig : sigs) { Trace.i(“MyApp”, “Signature hashcode : ” + sig.hashCode()); } I’ve used this to compare with the hashcode for my debug key, as a way to identify whether the APK is a … Read more
You can simply drag and drop the .apk file of your application to the emulator and it will automatically start installing. Another option: Windows: Execute the emulator (SDK Manager.exe->Tools->Manage AVDs…->New then Start) Start the console (Windows XP), Run -> type cmd, and move to the platform-tools folder of SDK directory. Paste the APK file in … Read more
Try changing the ADB connection timeout. I think it defaults that to 5000ms and I changed mine to 10000ms to get rid of that problem. If you are in Eclipse, you can do this by going through Window -> Preferences -> Android -> DDMS -> ADB Connection Timeout (ms)
Easier way than previous answers: Put this into ~/.gradle/gradle.properties RELEASE_STORE_FILE={path to your keystore} RELEASE_STORE_PASSWORD=***** RELEASE_KEY_ALIAS=***** RELEASE_KEY_PASSWORD=***** Modify your app/build.gradle, and add this inside the android { code block: … signingConfigs { release { storeFile file(RELEASE_STORE_FILE) storePassword RELEASE_STORE_PASSWORD keyAlias RELEASE_KEY_ALIAS keyPassword RELEASE_KEY_PASSWORD // Optional, specify signing versions used v1SigningEnabled true v2SigningEnabled true } } buildTypes { … Read more