Hi I have made a simple app and when I want to test it I connect my phone 1 to computer by USB cable and the app run very good then I share the app to my other phone 2 and other phones from phone 1 and when I try to install it on the other phones it says can't be installed.
Is the issue from phones or from the app I wored if I publish it on Google play
It's doesn't work pls help me.
The error appears because Android Studio signs your apk with the debug.key by default. Documentation is here. When you sign it with the release key as Google Play requires, the problem will go away.
Installing an app on your phone requires that the APK file is signed with a certificate. When you install an app to your phone with Android Studio, it generates a keystore with a certificate and signs your app. This generated keystore is insecure and can only be used for development. Most likely your other phone is not allowing you to install the app signed with this insecure key.
To fix this, you need to generate a certificate to sign your APK with. For instructions how to do this, read the official documentation
Related
I have an android app that i always upload to google play as an apk with a keystore from 2018 and I use google signing which is recommended as they say, recently I signed the app and exported it as an aab with the same old keystore but now old users can't update the app and new users can't install the app
Can anyone help me please ,is What i did is wrong and if so How to fix it
I have an app in the playstore created with kodular (similar to appinventor),
I started over with flutter and I like the result
However, when I try to deploy on the playstore, the app is refused with a reason: Your Android App Bundle is signed with the wrong key.
Do I have the upload_cert.der file, and how can I sign the flutter app with that certificate?
(i use android studio)
Your Apps key should match otherwise you will not able to update the apps. You can find the keystore in kodular
We have a Java based web application and an android app for our enterprise needs. We would like to remotely push the android app from the web application and we don't know how to achieve this. After searching in Google, I found Android EMM but did not understand what that is exactly as there were no other blogs or tutorials other than the Google site which was difficult for me to understand.
It is similar to MDM solution but do MDM servers have an app preinstalled in the devices so that the installed app manages the installation of other apps?
Can anybody tell how to remotely push the android app from my web application?
To remotely push an app to an Android device you need to manage this device, you cannot just push an app on anyone's device. To manage a device you need to set up this device as managed, which will require a factory reset.
If you want to pursue this approach you can try the Android Management API.
You can just upload .apk file to your server and provide a link to the user. This is a very simple solution but requires user to agree "install apk from third party sources". In this case, a user needs to agree with installing apk.
If you want to install apk without user agreement you need to activate Device Owner on Android (Fred mentioned in the comment this approach).
I am developing an app that uses google's turn based multiplayer API. I have two devices that I am using to test on. The first phone, which uses the developer gmail, can sign into the multiplayer just fine. The second one, whether I install the app directly from the computer or I install the signed apk with the release keystore, gets this error every time I try to sign in with it:
Failed to sign in. Please check your network connection and try again.
The second phone uses a gmail account that is set as a testing account for the app in the developer console. I am not positive what the issue is here. And yes, I have made sure that there is not an actual network issue as I am able access the internet just fine.
I appreciate any help. Thanks.
After troubleshooting for a while I realized that my issue was that my SHA1 fingerprint for my signed apk and the SHA1 fingerprint for the project that I had setup in my google developer console were different. To fix this I just unlinked the application from my game and relinked it using the correct SHA1 fingerprint.
To create facebook android native app we need to provide our Android application signature in facebook app settings. whenever i export some test application and provide the key and class name on application it is working perfectly , i am wondering how to make that workable on emulator... how to create a keyhash in emulator ... any ideas?
FYI i am following the tutorial below
http://www.androidhive.info/2012/03/android-facebook-connect-tutorial/
The app which is installed on emulator from eclipse is typically signed by default android debug key store, You will generate key hash from using that android key store, add that hash also to the your facebook app setting for android app, So there will be two hashes, one for debug keystore and the second one is generated by the key store which you will use to sign your app to test on real device.