I need to know that is there any other app or source code in android who can restrict or authenticate before installing other apk. Means if some one knows device pattern and try to install any apk, before installing apk need to confirm with some password or pattern to go forward. Thanks
Related
I made one application in Tizen studio and created a signed certificate(Author and distributer).
So now I want to create a signed package and send it to someone.
How to do that can anyone guide me?
Thankyou
If you just need to send someone your signed app it's very easy and you only need to right click on your project name and select "Build signed package"
But be aware your signed app can only be use directly into yours linked devices via SDK and no one could install it in other devices (at least, not directly).
The only two ways to use your app in real devices without SDK tools is publishing your app into the seller platform or through USB using the "Demo Packaging Tool" if your are a Samsung partner
You should check more about signing flow and publication process
I am developing an Android application and it is not finished. I would like to test it on multiple devices, locations with various users that are not near me. How can I achieve this? Is there an APK I can send them? Is there a way that is as simple as plugging my phone in and then running the application from Eclipse? Or would I have to make an installer of some sort (I don't know)?
Obviously you can plug your phone(s) into the machine you are developing on and run it from eclipse. This will allow you to test and debug on the devices you have access to.
You can also export an apk from eclipse (see the android pages for instructions). You could put this up on a file sharing site and make it available to your friends. They could then install it, as long as they have authorised "unsigned" apks to be installed in their phone settings.
Assuming you have deployed the app at least once from within Eclipse to debug and test yourself, you will most likely have an APK under the bin directory in your Eclipse project. The file should be .apk. This APK will have been signed automatically by Eclipse with your debug key. This is obviously not the key you use for publishing but for testing among friends I think it's fine.
What I often do is just e-mail that APK file as an attachment to my friends to an e-mail account they have setup on their phone. Then all they need to do on their phone is make sure they have the system setting to allow installation of non-market apps (i.e. not from Google Play), which maybe named something slightly different like "allow 3rd party apps". Then they can simply click on the app attachment in their e-mail, download it and run it and they should automatically be prompted with instructions to install it.
I just used MyAppSharer. (I believe there are other similar apps out there - this is just the one I've used and is very simple/easy:
...you can share by market link or directly share APK (App's full
package)
I just used that, and sent my app via apk file to my coworkers. Can't get much simpler.
Just install the app on your phone via Eclipse, then run this AppSharer, and voila - share it w/ anyone!
You can can easily export your project as an APK in eclipse
File -> Export -> Export Android Project
I has build an .apk with a server but I can't install it on a android device keytool:
INSTALL_FAILED_NO_CERTIFICATES
How can I publish my application without certificate ?
You can't. No app store will let you upload an unsigned apk, and even if they do, no Android device running an unmodified version of Android will let you install the apk without a signature.
This is why even eclipse uses a debug certificate to sign your app during the development process. Additionally, certain APIs and libraries like Google Maps will not be usable without a signed binary.
It is not difficult to do. Here is a link with just about everything you need.
If you want to upload it to any appstore, you can't.
If you want to send it to people that knows you and trust you, it can be done...
On the end user phone system menu, choose Settings/Applications/Unknown sources, then install from SD card, file attached to an email or any other source
You can self sign your application as explained here: http://www.androiddevelopment.org/tag/apk/
Any1 plz help me ... in android
How to update the complete apk which is already installed in end user device....
Say for ex: Android market app which is installed in device is completly changed to googleplay apk...
how to do that....
Thanks in Advance...
If you want to upload a compleatly new apk (like whole new project) just keep the same Key when signing and the same Package name (e.g. com.example.App) and it will update like magic.
You can do what NStorm mentioned, but if you have Android Debug Bridge installed you can open up command prompt and do an adb install like the following:
adb install -r file.apk
As long as its the same signing key and the same package name you will be able to install it that way. If you have a different signing key you will have to uninstall the application on the phone first to install it. The -r flag means reinstall and keeps all the previous data for that application. This of course only works if you have adb installed and if you physically have the phone and cord in your hands.
The other choice you have is to email the phone the application, or to host it on a URL page and have the end-user go to it and install it that way. You can easily upload it to a server and text or email out a link to the end user and they can reinstall it that way. You will still need to have the same signing key else they will have to uninstall the application.
In summary, you have three ways of doing it without going through the Google Play marketplace.
Upload to a server, and text/email out a link to the apk.
Email the apk as an attachment, have the user download and install.
Use ADB.
I created a .apk outside of eclipse using tiggr mobile (http://gotiggr.com)
i have the downloaded .apk and need to sign it - so i thought about running it through eclipse then signing it that way
im having the worse trouble importing it into eclipse.
does anyone have any other suggestions on signing this? i keep getting this message when uploading:
Market does not accept apks signed with the debug certificate. Create a new certificate that is valid for at least 50 years.
Market requires that the certificate used to sign the apk be valid until at least October 22, 2033. Create a new certificate.
Market requires the minSdkVersion to be set to a positive 32-bit integer in AndroidManifest.xml.
thanks for your help!
It would be faster to get the source code into eclipse via retyping it than to try and unsign and explode the apk, edit the manifest, fool the tools and sign the package. The tools can be run at the command line anyways and eclipse would just make it harder.
One problem you have is that there are problems in your manifest. The market requires some attributes set in it that you did not need while doing developer builds. You can open up the apk with anything that will open a zip file. You can edit text files with notepad. You package them up with ant by recreating the build.xml by hand. The instructions for signing things is here:
Android Dev-Guide: Signing your Applications
But what a LOT of work... and I am guessing you will need to do this multiple times just for one release to get the manifest right. Then what do you do when you need to update your program?
Will the service not let you export the code in an easy to use way (because... wow... talk about evil)? Failing that cut and paste will save you time but you will almost certainly want to have it in eclipse or some IDE ready to make changes for your market release and build, package and to sign it.
That's not your issue. I suppose you compiled your app and now you're trying to publish it in the market. To do that, you need a private key whick in turn requires you to have a android market developer account.
Normally you can develop your app and install it into most devices but you can't submit apps to android market without a developer account.
If what you really want is only to import your app to eclipse, I suggest you to create a brand new android project and copy everything into it. It's easier and faster than adjusting everything!