I want to create an Android wearable app on Android studio. I have installed the apk file on mobile to test run it. I would like to know how I can run the same apk on wearable device.Also, apk file created on Studio is different for wearable and mobile devices. How can we run it? Thanks in advance!
As it mentioned at official website you need to create special package signed by release key. See more info about packaging here.
When developing, you install apps directly to the wearable like with handheld apps. Use either adb install or the Play button on Android Studio.
Note: The automatic installation of wearable apps does not work when you are signing apps with a debug key and only works with release keys.
During the development period, do not use release key for signing. Instead, you should build your app which would result in two apks, one for the phone and one for the wear device. Then install each of them separately on the corresponding device using adb or Android Studio. Make sure you are using the same package names for both apks.
When you are done with your development, then build the app with your release key; then the wear apk will be embedded inside your phone apk and installation of your phone apk on a phone will result in the installation of the embedded wear apk on the wear device (make sure you remove the dev apks from both devices prior to this step otherwise installation will fail due to different keys).
Trying to debug through Android Studio as suggested by Julia and Ali, but it is always showing me Parse error while installing or running the code.
I have created a project for both mobile and wear. While running for mobile it works fine in the mobile device but while running the code in the wear it always shows Parse error.
I am using Moto 360 for running and debugging.
Related
I gave a build for android using gradlew assembleRelease.
but app-release.apk file not working for some devices like honor 9i, Redmi note 5 pro.
Make sure your app is compatible with OS of your device. Enable installation from unknown sources. Sign your app before sending .apk. It is important due to security restriction of some devices.
signing your app
Happened to me on some devices as well. Even if you allow installation from unknown sources turned on. Some devices alter the final .apk file (maybe for security reasons). So we used android playstore publish for distributing app as test/beta builds. Pick one appropriate for your pre release distro. It should work fine.
I made an Android app using Android studio, deployed and ran it directly by using my mobile running Oreo.
It installed successfully. But later I tired to share the APK from my mobile to other mobiles. But none of them are able to Install it.
However, if I build the APK and share the app-debug.apk to other mobiles. It Installs successfully.
I can't build APK and share app-debug.apk it everyone.
I usually deploy it in my mobile, share APK(which used to work before)
Can anyone please help
Please excuse typos, I have typed from mobile.
There might be a signing issue. Is your app signed? The default signing is the debug signing. When you just build and deploy or run it on a connected device, it is signed by default as a debug sign.
If it is not uniquely signed, then running or installing on other devices might not be possible. Look at the app signing instruction and guide by Google, here, if you wish to distribute your app on other devices.
Another problem might be in the security authorization of other devices. Your device on which you are building has the developer options turned on. To run and install unsigned apps you'll need to activate the developer options in the device you want to run it on. Look at this link about Developer Options and how to turn it on.
by default the Android Studio packages just the needed files and installs the app in your mobile. If you share to other mobiles, the app will not install in few devices due to a few reasons like OS version, files mismatch, SHA keys mismatch, etc.
However, if you build the APK and share, the APK is equipped to be installed in any device starting from the minimum SDK version to the target SDK version.
I have created a demo project of wear in Android studio. So the two projects created automatically, the phone and the Android wear are linked correctly.
When I generate the apk of the phone project, the two apks are generated.
The phone apk I signed it and uploaded it to Google Play Alpha.
In generated phone apk, inside res/raw I can se wear apk. So the mobile apk contains the wearable apk properly.
I have real physical phone and Android wear emulator linked. When I link real device to emulator, in Android wear emulator my phones apps that have wearable version are installed automatically.
I download my app upload from play store alpha to my phone, but in my wear emulator wear version of my app is not installed.
Additional info:
-The wearable emulator does not contain any app with the same package name.
-I have done several tests creating a new emulator.
-In the emulator if I install the application directly with the play button of Android studio works correctly
The packaging and distribution of wearable apps changed with Android Wear 2.0. Wearable apps are no longer synchronized from the phone. Instead you need to upload a wearable APK to the Play Store.
In Android Studio we have two folders
Mobile
Wear.
So which apk should I install on my smartphone, which would sync the corresponding setup to the Android Wear?
DEBUG :
You can install the Mobile apk on smartphone and Wear on your smartwatch, with ADB & plugged into USB
RELEASE :
Just install the Mobile apk on smartphone, this will sync to your wear
So which apk should I install on my smartphone, which would sync the
corresponding setup to the Android Wear?
That's true only when the apk is exported and signed with the production certificate. When you develop, you have to explicitly install the apk, on both devices. You just need to switch between the wearable and handheld application on AndroidStudio, in the drop down menu next to the run button, and choose the device, in the popup which prompt the attached devices
Easiest way to install wearable apk :
Make sure your package name of wearable and mobile are same.Go to AndroidManifest .xml file both these module and check whether these are same or not. If same then ok otherwise you have make them same.
Normally, There two apk's are available in wearable project one is "Mobile APK" and another is "Wearable APK".
We have to build signed apk for "Mobile apk". If any one doesn't know how to build signed apk you ca see this video - Click here
When APK build successfully you can find it in "Your_Project\mobile" folder.
Then send it to your phone which is connected to wearable device.
Then install it on your mobile.
When the handheld app will connect with the wear, it will install/update the wear-apk on the wearable device.
The mobile app can be empty, without Activities, but you have to declare the same package in AndroidManifest for both.
I exported an unsigned apk file that represents a test version of my Android application. I need to distribute this to quite a few users. Is there a simple method to distribute the apk file where it will install the app? I'm trying to avoid the test users from having to download something like Astro or the sdk. Any ideas? I tried putting it out on a global web server and the file downloads but doesn't install. Thanks for the help!
From the android documentation:
The Android system will not install or run an application that is not
signed appropriately. This applies wherever the Android system is run,
whether on an actual device or on the emulator. For this reason, you
must set up signing for your application before you can run it or
debug it on an emulator or device.
So even if your users have the "Allow installing non-market apps" checked, your application will still have to be signed with at least a test key before it can be installed on a physical device.
I just put my experimental apps on the Android market with a description that says "don't install this, it won't work for you" and then give an access key to my testers.