Just now I have developed an application and now I am ready to upload it to Android market,
but when I am trying to upload, it shows the following error message:
Market does not accept apk signed with the debug certificate. Create a new certificate that is valid for atleast 50 years. Market requires that the certificated used to sign the apk be Valid until at least October 22, 2033. Create a new Certificate.
Now how do I fix this problem, so that I can upload the APK file to Android market successfully?
While developing and testing, you can compile in debug mode(debug certificate).
When your application is ready for release, you must compile in release mode and then sign the .apk with your private key.
The following link gives will help you
http://developer.android.com/guide/publishing/app-signing.html
Related
I'm trying to build a release signed Android app bundle file for my android app but I keep getting a Failed to start monitoring R9JN502ET6J notification at the Event log.
Might I be inputting the wrong password for my .jks file ?
I have tried to invalidate caches and restart but still getting the same output at Event log.
Trying to build an app for updating android OS built from source. Even after signing the app with the platform key, the method RecoverySystem.installPackage(context,file) when applied on an updatefile placed in '/data/cache' gives error that writing to /cache is not permitted for the app. Also, an SElinux error is thrown for trying to access /cache partition.
The app holds the necessary permissions android.permission.RECOVERY, android.permission.REBOOT and android.permission.ACCESS_CACHE_FILESYSTEM
Going through the source code, the lines
...
FileWriter uncryptFile = new FileWriter(UNCRYPT_PACKAGE_FILE);
try {
uncryptFile.write(filename + "\n");
} finally {
uncryptFile.close();
}
...
in RecoverySystem.installPackage() triggers the error.
(http://androidxref.com/9.0.0_r3/xref/frameworks/base/core/java/android/os/RecoverySystem.java#562)
Even though the error is displayed, the device still reboots to apply update but the recovery shows "no command" screen most probably as no commands are written to /cache/recovery
the OS build is user build and thus not rooted.
am i missing something? is there any other way for a platform signed app to install firmware updates for the user build?
Similar : Android development RecoverySystem.installPackage() cannot write to /cache/recovery/command permission denied
I followed this tutorial for adding Goggle Login to my App:
https://firebase.google.com/docs/auth/android/google-signin?authuser=0
So the Code is similar to this:
https://github.com/firebase/quickstart-android/blob/master/auth/app/src/main/java/com/google/firebase/quickstart/auth/GoogleSignInActivity.java
But when signing in i get this...
Error:
Google sign in failed
com.google.android.gms.common.api.ApiException: 10: at
com.google.android.gms.common.internal.zzb.zzz(Unknown Source)at
com.google.android.gms.auth.api.signin.GoogleSignIn.
getSignedInAccountFromIntent(Unknown Source)
I think I've setup the firebase and Google Console right. Also the Android Studio Assistent for adding firebase, says that the dependencies are correct.
What do I overlook?
I went through this problem and after much sweat I discovered that the problem was the wrong SHA1 key.
you have to generate a sha1 debug key while it is in the development phase. After launching your app you should use your release key.
for generate debug key, open keytool.exe and: keytool -exportcert -list -v -ali
as androiddebugkey -keystore %USERPROFILE%.android\debug.keystore
passwd: android
done this, copy the generated sha1 key, in the firebase go to configuration of projects, add fingerprint. done this, download the json file for your project and run.
you must repeat this procedure with the sha1 release key.
I figured it out. Was kind of dump. I started an Project in the Google Console and later in Firebase. Then I tried to connect them to use the Webclient-Id...
After all they where not combined so Firebase didn't find this Web-ID.
-> I just created a new Firebase Projekt and out of there created a new Google-Console Projekt where the Web-ID is generated. After implementing the new Web-ID in my App it worked fine!
I imported an android studio project from another developer to my system while generating Signed APK I am getting this error.
Error:Execution failed for task ':app:packageRelease'.
com.android.ide.common.signing.KeytoolException: Failed to read key mobile_visit_confirmation from store "C:\Users\ABC\AndroidStudioProjects\myapp\myapp_Key_Store.jks":
Keystore was tampered with, or password was incorrect
The project was done by someone now I am working on that he is not providing password, alias and certificate information and I want to upload update APK to play store.
I am trying to publish a simple project in android studio .so i go to menu>build>build apk .but i get this error :
Error:Execution failed for task ':app:packageDebug'.
> Failed to read key AndroidDebugKey from store "C:\Users\ehsan\.android\debug.keystore": Invalid keystore format
I am so new in android studio
I'm also facing same issue. for mine getting this type of issue, when I run app with my physical device.
Solution
Delete .android (path:C:\Users{your pc name}) folder in your work space then try with step by step process.
good luck