Hy I am trying to package the wearable app using Android studio 1.0.1 and I am following the steps given on this link https://developer.android.com/training/wearables/apps/packaging.html and I followed the steps over 3 successfully . but when go for 4th step , that is to click the Build menu on AS and to click the signed apk , but after that I got a selection box , weather to sign the mobile apk or to sign the wear app.
Now this is a point which is confusing for me , Should I go for Mobile app and It is all done and I would be able then to install the app on mobile and it will push the wear app to wearable or should I first signed the wear app and then paste this signed app in the mobile app and then select the sign mobile app , ??? what should I do to make it work
I think that my question is quite clear now. waiting for help
You have to simply create a module of your wear app with the same applicationId. In addition you add to your gradle script file of your mobile app:
dependencies {
//something bla bla
wearApp project(':mywearable')
}
Generete from Android Studio menu your release APK for your mobile app. You'll see actually that two apk are generated, the mobile and the wear apk but it's only a convenience for you. If you check the mobile apk you'll see the wear app inside, so don't worry use always to publish the mobile apk.
You should build and sign your just mobile application. Wearable aplication will be signed automatically and introduced inside mobile .apk
You could check this opening the .Apk generated as a .zip. Wear apk will be in res/raw/ folder.
Related
I am a little bit confused about two differents behavior and I would need some help.
I am working on an android application with App Links implemented.
I have configured my project to use a keystore for Released build version.
When I use RUN Application of Release version from Android Studio, my application will be opened as a deeplink (disambiguation dialog open when click on a link).
When I generate a SIGNED APK using the same keystore, my application is opened as an app link (direct to the app without dialog).
I have analyzed the two apps (Build APK & SIGNED APK):
RUN Application : App Link status is in ask mode when application is installed;
Signed APK : App Link status is in always mode when application is installed;
Is anyone could explain me what are the differences between RUN Application and Generate Signed APK which could lead to these two different behavior ?
Thanks
Build APK: this is testing APK you can say.in this, we don't need to use Keystore. And in this build Keys are not restricted as we use in Google maps or Facebook SDK. Not big
Signed APK: This is purely a live build you can say. we use live credentials in this build we normally won't use this build for testing.we generate Signed APK after complete testing normal APK.
BIG DIFFERENCE is that play store only accept the SIGNED APK.
So we generate signed APK normally when we have to submit our app to play store.
I am assuming you created the assetlinks.json using the release keystore.
Actually, in regards to app link, there is no difference between the RUN Application(release build) and the Signed APK.
The verification of the assetlinks.json file is done during the app installation. When you run the application from the android studio, the disambiguation dialog is showing because in the device, you might already have a pre-installed version of your app. So when you run the application, the app is not uninstalled and then installed. It just refreshes the code. So the assetlinks.json verification is not done.
So to test app links while running from android studio, first uninstall the app from the device/emulator, and then try triggering app link. The disambiguation dialog will not be shown.
You don't have to uninstall the app every time you want to run the application. But if you have changed the assetlinks.json file(at server side) or the manifest entry in manifest file, then uninstall the app and then run the application(release build) from android studio. The disambiguation dialog will not be shown.
I developed this react Native mobile application called "ClkApp". I Published my application using expo and I can see the application on my phone.
Now, I want to publish this application on Google play. I completed all the required steps including paid the fee of 25 dollars. One of the step requires that I generate a signed APK. I saw some tutorials how to generate the Signed APK and all of them build the application using android studio and go to Build -> Generate Signed APK. I tried to open my app on Android studio, but I don't see any option under Build menu other than "Analyze APK" and "deploy Module to app engine". there is another option called "make", but that is disabled. Below is the image:
I created a new test application using android studio and I can see the options like generate signed APK, Build etc. for this test application. I don't want to create "ClkApp", my original app", application using android studio because that will take lot of time. Is their any way, I can generate the APK on this existing application and don't have to use android studio at all.
Any help will be greatly appreciated.
Since you have build your app with Expo. You can use Expo to generate apk (standalone app)
After you configure app.json and run expo build:android
Check this for details https://docs.expo.io/versions/v32.0.0/distribution/building-standalone-apps/
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.
I am creating a watch face for android wear. After creating watch face and reading this, I have generated signed apk for android wear.
But android studio is generating two signed apk: one for mobile device and another for wearable.
I want to pack my wearable app inside my mobile app so that watchface appear on companion app as shown on developer's guide.
I installed mobile-release.apk but when I open it it doesn't showing in companion app or anywhere. Can anyone help me how to install it?
Assuming you use android studio:
Your mobile build.gradle file should have the following dependency:
dependencies {
...
wearApp project(':wear')
}
Go to Build > Generate signed apk. In the first window, select mobile as your module.
Now when the build is complete, the wear module will automatically be embedded into the mobile module. The mobile apk is the one you distribute. Wear can be used for testing.
Hi i am new to android development.
I am creating one application. I need to send sample application to client for testing purpose.
In iPhone development we can send .ipa file to client using TestFlightApp. Is there any way to do this similar way for Android application testing.
Please help me in this issue.
Thanks in advance
each time you build your application, an apk file is created in your project's bin folder. you can use that file for testing purposes
Right click on your application project folder
Scroll down to Android tools
click on : Export as signed Android application
Use the debug key located on your sdk folder to sign the app
,the password's key : android
and you will get a debug signed apk ready to install on any device .
To keep track of your apks you may create a string variable and use it as build tag so you don't get confused by multiple apks .
I'm doing so on my project , you can also create an unsigned apk but I don't know if you will be able to install it on a real device .
Some use maven to build the apk but it's more complicated .