The Android system requires that all installed applications be digitally signed with a certificate whose private key is held by the application's developer. The Android system uses the certificate as a means of identifying the author of an application and establishing trust relationships between applications. The certificate is not used to control which applications the user can install. The certificate does not need to be signed by a certificate authority: it is perfectly allowable, and typical, for Android applications to use self-signed certificates.
You can use self-signed certificates to sign your applications. No certificate authority is needed.The system tests a signer certificate's expiration date only at install time. If an application's signer certificate expires after the application is installed, the application will continue to function normally.
-from android.com
Signing is the process of giving a e-signature to an android App . It is necessary for an app . Only signed apps can be opened on an android device or an emulator .
But today I am going to introduce some apps which are you really helps you to sign your apps .
1 . ZipSigner
------------------
It is a best app . It allows users to sign their apk through their mobile phone .
It can be download directly from Google PlayStore .
Link : https://play.google.com/store/apps/details?_e_pi_=7,PAGE_ID10,1873588905
2 . JarSigner
---------------
Better app . But needs windows OS . We can easily sign applications by this tool .
3 . KeyTool
------------
Also a best tool . Its simple UI helps users to sign their app without complication .
After signing zipalign tool makes app from zip .
Hope I helped . Don't forgot to hit thanks button .
Thank you .
Sent from my GT-S7562 using XDA Premium 4 mobile app
Related
Hello, I have a question, I already read like 20 Threads on here and still haven't found a solution.
I have developed an android application that only gets installed on selected devices (for example the Google Nexus Player (fugu)). The app relies on root permissions, currently I am using a rooted device with su, but I want to build it properly. I don't want to publish the app in the playstore, but is it possible to sign the application as a System Application with sharedid="uid.system" ? If so , how can I do that ?
Regards
Hi, I'm trying to run the Android Device Policy app on Bluestacks so I can manage the device by https://enterprise.google.com/android/experience/overview.
However for some reason the app cannot complete its set up and it shows an error: "Your System cannot be managed by this app. Please contact your administrator."
I have tried to root and allow all the permission to the app, but it still does not work.
Any suggestion?
Regards,
I had encountered this problem previously, and after a deeper Google search found out that there is a way to make this work.
Don't try to apply the policy through the Android notification
Open Play Store
Search for Android Device Policy
Install it
Open it
Set your lock screen if requested in the Policy app
Once complete, your device should be registered and able to sync.
NOTE: I only have tried this on the new Beta 5 version of BlueStacks. It worked great.
HTH
Hi,
I want to mod Whatsapp on my own without using third party apps such as GBwhatsapp , Whatsapp plus, parallel space apk, appcloner apk...etc. I want to know how they do it.
What i Found
I tried using an android application that clones whatsapp and found there is two methods used:
1. Workspace Method: Parallel Space installs whatsapp in the root folder of the Parallel space application it self without changing in the code or any thing. There is several apps that do the same. ( I am not interested in this method)
2. Apk editing method: Appcloner apk, it clones whatsapp to a different name and allows modification to the app, but on one condition the original whatsapp version must be installed in order to verify the whatsapp number. (This is what i am trying to do manually) but i need to solve the problem where i dont need to install the original app in order to work(gbwhatsapp solved this problem but how?)
What i tried:
A.
I tried decompiling the whatsapp using (apktool, ApkEdit) then signing the app using zipsigner. The app gets installed but the problem is i cant get pass whatsapp verification number it gives an error and returns whatsapp to the first page:
"Something is wrong with your version of whatsapp. Please download the latest version from our website: https://whatsapp.com/android."
This is the error that i face and i want a fix for it.
B.
I used zipsigner on the original whatsapp apk file and signed the apk with new signiture then installed the app. I found that it gave the same error as above.
Conclusion:
Changing whatsapp apk signature prevents you from verifying the whatsapp number.
Can any one provide us with a fix how can we do this and mod our own version of whatsapp. I presume there is something to do with exposed since i found exposed modules in the decompiled folder for the cloned Whatsapp apk by appcloner and the apk gbwhatsapp.
Thanks
Related post:
https://forum.xda-developers.com/android/general/how-to-mod-whatsapp-t3872019
I have setup multiple users on my device (even though I am the only one using my device) and things are not working perfectly, or the way I want it to.
The issue is primarily with side-loading apps on secondary users.
Even though the multi-user environment appears to be completely isolated, that is not completely true. An app can be installed on the device only once. When installing the same app for different users, app installation happens only the 1st time. What happens during subsequent installations is simply creation of a separate data folder for each user. That is why one can't install different versions of the same app for different users. Installation would always fail if such a thing is attempted, unless the newer installation is an update to the app version already installed on the device (in which case all users with the app installed will see the same updated version).
When side-loading, some apps just fail to install in secondary users. Does anyone have an idea as to what could be possibly wrong? These are free apps (often downloaded from Google Play Store), so there is no license verification issues. This can happen irrespective of whether the particular app is already installed for another user or not.
Is this a bug with the whole multi-user feature or is there something that needs to be done to get this working?
I have tried this on three different devices (rooted as well as non-rooted), running on Android 8, 9 and 11. They all seem to have similar problems. Some apps install, and some don't. Is this an Android problem or an app-related one?
Please note that apps that fail to install in secondary users, install and run perfectly fine on the main/ primary user. So this isn't an Android version compatibility issue, but one related to the multi-user feature of Android.
Thanks.
Look inside here:
Building Multiuser-Aware Apps | Android Open Source Project
source.android.com
jwoegerbauer said:
Look inside here:
Building Multiuser-Aware Apps | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks for the link. I was almost tempted to believe that the problem could be with the apps not supporting multi-users. So I did this to test:
I created 2 secondary user accounts.
On one, I signed in with my Google account and installed some apps from the Play Store. I copied their APKs.
On the other user, I did NOT sign in with any Google account. So I can't access Play Store. I tried sideloading these APKs. Some got installed, and some didn't.
Are these apps (that failed to install) somehow dependent on Google Play Store for installation? The fact that they installed on the user who signed in with a Google account means that they support multi-users. So we can rule that out.
I tried MiXplorer and it successfully installed on both users.
jwoegerbauer said:
Look inside here:
Building Multiuser-Aware Apps | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
I think I have figured out the problem.
Apps that refused to install were actually Split APKs, and I was trying to install the base apk file extracted using a file manager.
Backing up the App Bundles for such apps using SAI and installing them worked perfectly.
Hi all,
I have been trying to install the app I developed on my google pixel 4a but fortunately I can't install the app due to the error " the package conflicts with the existing package name "
how can I overcome this
Thanks
It appears the package name you have for the new app is the same as another app you already have installed on your device.
So, you need to change the package name of the new app you are developing to a name that is unique just for your app so that it is not the same as any other app.
Rename package in Android Studio
How do you rename packages in the new IDE Android Studio, based on IntelliJ IDEA? Is there an automatic refactoring included? I want to make bulk refactoring, but I don't know how. I worked two ...
stackoverflow.com