I have developed an app which is ready to launch on play store.I have signed the app as ionic app publishing documents said.When my signed apk was ready i copied the apk to my device and tried installing it but, it says 'You cant install this application'.I dont have any previous apk installed on my device.I have tried opening the signed apk in android studio and tried installing it from their, it worked.I just want a confirmation that should i upload this apk to playstore or do i need to find the bug.
I followed these steps
Related
I am converting my angular PWA to APK .
I followed same tutorial as this link:
https://medium.com/#christof.thalmann/convert-angular-project-to-android-apk-in-10-steps-c49e2fddd29.
I am able to create APK without signing its opening correctly .
I created keystore and I signed , after signing and generating new
APK,while installing app is showing App is not installed.
Any
help is highly appreciated
I have already signed and released an apk on playstore using Eclipse. Now I have started using Android Studio. Now When i enhance the same app with the same keystore value , and test the apk should'nt it update the same app in the device, it installs a fresh Application. The project is migrated from Eclipse , It has the same package name obviously. It is in debug mode, Should it update the same app or install a fresh new application during debugging??
Using the keytool tool in the JDK 8, I signed my APK and successfully uploaded it to the play store. However, once I downloaded it, it said, "Package was not signed correctly". Does anyone know how to fix this?
Do you have your debug version of application still installed on your
device?
If yes, Now you have downloaded a different copy of the same app and it's causing this error.
Uninstall the app completely from your device. Then download it from the market again and it might work.
Another reason
I did a quick research and In Many links and Blogs, people seem to have faced the similar issue and they have started using jdk 6 and signed their app and uploaded to playstore again.
Published Android apk gives error "Package file was not signed correctly"
http://developer.appcelerator.com/question/146110/my-app-gives-package-file-was-not-signed-correctly-error-on-google-play-store
http://support.ludei.com/hc/communities/public/questions/200781567-Google-Play-error-Package-file-was-not-signed-correctly-
Hope this information helps.
When the app in the development stage, I get the apk from the "bin" file and install it in a real android phone to test the app, and it works great. However when I export the apk from the eclipse, the apk can successful export but the apk cannot install in the phone, and shows
An existing package by the same name with a conflicting signature is already installed
Some people said you need to uninstall the app and install it again, but this app I want to put it on the Play Store, so it is impossible to ask users to do this.
Also, I want to use the ProGuard function, so I need to export the apk to enable this function.
Your development APK is signed with a development key. Your production APK is signed with a production key.
When you try to install a production APK over a development APK, it detects that the keys were different and refuses to "upgrade" the APK.
For production in the Google Play store you won't have this problem. All your users are already using the production version of the app. The new APK you provide is also a production version and so since the keys match, the upgrade will work without the users needing to uninstall the app.
Uninstall the app on your phone then re-install it
I am working on the In-App tutorial and I am getting an error saying the version is not configured for billing through Google store.
There may be some confusion as to the version being used on my device.
This is my normal process
I have a signed key that has been setup and does work properly
I use Eclipse and I build my app there I build it constantly buy clicking the build icon and if my device is connected it opens on the device I do not sign anything that I know of (which leads to some confusion)
When I want to release the App I export it with the signed key and I have to export signed Application Package in the Android Tools I see when I right click on the App. An .apk file is generated and I upload that to google and everything works.
My question is when I simply run the App on my phone and it comes directly from eclipse what mode is it in
The In-App tutorial says I must be running the signed version on my phone.
Am I doing this automatically when I start it from Eclipse or is it in debug mode.
If it is debug mode how do I make it go into signed mode from Eclipse.
The version I need to upload to google is signed but is set as UNPUBLISHED as stated by the guide in the tutorial so I can not get it from the store.
To test anything that has to interact with the Google store, you need to use the release version of the .apk file. Export it as usual from Eclipse, then use the command line tool to install the release .apk on the device or emulator:
>adb install myApp.apk
If you previously ran on the same device or emulator from within Eclipse, the app will have been signed with the debug cert and you will have to completely uninstall it first. Even the -r switch on the apk install command won't install if the signing certs are different.