Over the weekend something happend, because on monday it wasn't possible anymore to make a signed production build of my App. The only thing that I installed was Ableton Live 11 but I don't see how this could be related. I use "Generate Signed Bundle / APK" to make sure the signingConfigs in build.gradle are not the problem.
When running from Android Studio it showed this:
When uploading the APK on APKPure it showed that the apk wasn't valid:
Steps that I've tried so far:
Tried different projects, all projects are unable to sign, so it's not the specific project.
Uninstalled Android Studio from this SO thread.
I've found the Signature mentioned on apkpure in google-services.json and I've deleted this, but same result.
You probably changed the KeyStore of your app.
Make sure that in build.gradle, the signingConfig-attribute of debug{} and release{} in buildTypes{} have the same value and debug{} has the attribute debuggable true
Source: https://stackoverflow.com/a/27873028
Related
I have a multi module project that I just inherited. I'm able to build and debug the app as well as create signed APK. However, when I try to clean and then make the project (release flavour) the build fails. Error generated refers to a theme that connot be found. I did verify that the theme is present in one of the modules.
I'm going to spend some time to figure out why the theme is not found when I make release flavour. However, I'm somewhat confused why creating signed APK (also release flavour) works. I always thought that in both cases a similar gradle script is being executed.
Can someone please explain the difference, if any?
I'm using Android Sutdio 3.3.
File --> Invalidate Caches-->Restart
then from build--> make project
I think this can solve your problem
Have these erro when i'm trying to build the apk to some devices. Have no idea whats going on.
I get that when i build and install apk on device at the first time.
Someone have some tips for that?
[[EDIT]]
Well, after creating a debug key on keystore, i can build and deploy the apk via ADP to the device. But, dont know why, the error just return...
And now, we have other error:
UPDATE:
I Fix that issue removing all Android SDK and Android Studio and ReInstall it.
The problem can be solved by addding the install flags -r -t in the Run/Debug Configuration Dialog like it's showed in the given image
You can find Run/Debug Configuration Dialog location here according to Jetbrains.
UPDATE: Depending on the Android Studio version the Run/Debug Configuration position in the IDE can be slightly different, but always refer Jetbrains to find whatever you are looking for
When you've installed an APK from another source, Android Studio warns you before overwriting.
For example, if I've developed an application, uploaded it onto the Google Play Store, downloaded it, then try to re-deploy that same application from Android Studio, I'll get this warning.
It's trying to tell you that the way the package is signed is different; it's warning you that another app might be masquerading as the original.
The reason is you are trying to install the application with the same package name.
If you have already downloaded the same application from the play store /app market, then simply uninstall that application and RE-RUN.
This error can also occur if you recently switched branch which had different build variants declared in build.gradle file and you didn't perform gradle sync.
For example you had release and debug and then you switched to branch which has releas, deubg and staging variants; your project will still build but while installing apk this error can pop up.
My app works perfectly when I install it using a usb cable. When I download using HockeyApp or Google Drive it installs, but when I click the app icon it says 'App has stopped'. It will not open the application.
I am using React-Native and Android Studio to build the apk. I generate a signed release and check both signature (v1, v2) boxes.
Any ideas on what the issue could be?
****Edit Fixed****
Thank you for all the suggestions.
I have no idea what changed but I started getting a different error so was troubleshooting the new one and everything started working.
Answer of the following post worked:
error "Could not get BatchedBridge, make sure your bundle is packaged properly" on start of app
For installing an app from any unknown source, you must check it is released app as you define that app is released version then there may be any duplicity in the manifest file.
If you want to check what is the error you must run app from Android Studio and change build variant to relase and for debug app in relase mode
release {
debuggable true
}
it will show what error is comming when you start app in Android Monitor
I'm found similar apk install issue 1month ago
Crash on app(app is New project)
but I’m found resolve way for this problem
The way is add jackOptions, gradle
jackOptions {
enabled true
}
..I have no idea, Why this problem is resolved..
But resolved this problem
good luck
What are some notable differences that a developer should take note?
The first one is debuggable and the second one isn't.
That means that the first one will output all your Log.d's and the production version won't.
Also, by default, debug versions are compiled without ProGuard while production builds are compiled using the default ProGuard rules
you may take a look at those posts
Android Studio: Build type release /debug - what relevance does this have?
also the officiel documentation is clear and hepful
http://developer.android.com/tools/publishing/app-signing.html
hint
debug when you are working on the project
release when you are about to publish the app
good luck !
One of the most important differences is that debug version of app is not prguarded so it can be reverse engineered. The reason why it's not proguarded is because you can track your logcat outputs easily without need to check mapping files.
In debug mode, you sign your app with a debug certificate generated by the Android SDK tools. This certificate has a private key with a known password, so you can run and debug your app without typing the password every time you make a change to your project.
I get this error while trying to upload an apk on google play:
You uploaded a debuggable APK. For security reasons you need to
disable debugging before it can be published in Google Play.
I am using phonegap build (version 2.9)...I still uploaded an apk for the same app about 3 weeks ago without any issue. The solutions I found online has to do with the android manifest file which phonegap build doesn't have...
I think in BuildConfiure.java make DEBUG = false; while deploying .apk i think we should make it false
Had to edit the app with with apktool, made the change to the AndroidManifest.xml, then re-sign with jarsigner and finally wrapped it up with zipalign....it uploads correctly now...I guess the problem was that phonegap build changed the way they build android apks
Add
android:debuggable="false"
into manifest.
And also back to the PhoneGap Build interface, clicked Settings, unchecked the "Enable Debugging" box and then recompiled.