I must be missing something simple. I have developed a watch face, but when I build the mobile apk it never makes it's way to the watch. If I build the wear apk, everything works as expected.
Things I have checked so far.
Permissions: I have set the permissions in both the wear and mobile AndroidManifest
<uses-permission android:name="com.google.android.permission.PROVIDE_BACKGROUND" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
Gradle build: The wear app is referenced in the build.gradle of the mobile app.
wearApp project(':wear')
Things to note, The mobile app does nothing other than be a carrier for the wear app. It does not have any Activities.
You have to generate a signed APK and install it manually on your phone with the Android Wear companion app.
Related
I am new to flutter, I am creating a flutter app where I am using different APIs(Third-party APIs).
While running the app on the emulator, It's working perfectly fine but when I generate the APK for it and install it on my phone, it's not working.
All the design and layouts come perfectly fine but when I am about to hit login API, Nothing works.
Thanks in advance.
For release build, you have to add internet permission in AndroidManifest.xml file that is located in my_flutter_project/android/app/src/main/.
<uses-permission android:name="android.permission.INTERNET" />
<application
android:name="io.flutter.app.FlutterApplication"
...
What i am trying :
I am new to the WearOS development. I am trying to create standalone app (for 1.x and 2.0) and share it for testing.
As I mentioned standalone app, it's not dependent on any mobile devices, neither Android or Apple phone.
What i have tried :
I have tried releasing an app to PlayStore as an "Internal test" and as a tester, I tried to install the app by web PlayStore install button. The PlayStore shows "... will be installed on your device soon". But still, it's not installing the app. My wear is connected to the internet but no luck.
Manifest Entry:
<uses-feature android:name="android.hardware.type.watch"/>
<meta-data
android:name="com.google.android.wearable.standalone"
android:value="true" />
<uses-library
android:name="com.google.android.wearable"
android:required="false"/>
Question :
Is companion app is needed for standalone wear app? OR may be if you know and can share any suggestions to share standalone wear app.
From WearOS 2.0, PlayStore is available on wear. So, When we open app page on PlayStore and install from there by selecting wear device, wear 2.0 devices are able to get the app directly through the PlayStore without companion app.
I had an app uploaded in google play, but now I have done a update with Android Wear. I have my project in Android Studio with the mobile and the wear APK in the same project and with the same package. It runs perfectly in debug mode. I can export the new update of my app with the Android Wear app embebed, but when I upload it with the Google developer console shows that there are only one compatible device.
Attached Images:
How can i make my wear app to be compatible with more than 1 device? :-)
You shouldn't have the permission android.hardware.type.WATCH in the Play Store permissions.
This is only required for the wear application.
Remove it from your AndroidManifest.xml mobile application, it looks like:
<uses-feature android:name="android.hardware.type.watch" />
I have my AIR application created in Flash Builder 4.6, and trying to debug it on the device via USB. Application gets deployed properly, but doesn't connect to the internet. I have permissions set properly to
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
When I export release build and deploy it on the same device, it gets connected to internet without any issues.
Any ideas how to fix it?
Here is the stuff that matters from my Android App Manifest file. I am looking at supporting Android API Level 4 and above with target = 14 supporting all screens.
Developer console shows
API level: 4-16+
Supported screens: small-xlarge
OpenGL textures: all
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"></uses-permission>
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"></uses-permission>
<uses-permission android:name="android.permission.INTERNET"></uses-permission>
<uses-permission android:name="android.permission.READ_PHONE_STATE"></uses-permission>
<uses-permission android:name="android.permission.WAKE_LOCK"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_COARSE_UPDATES" />
<uses-permission android:name="android.permission.WIFI_CHANGE_STATE"/>
<uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/>
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true" />
Here is the Google Play App link
Here are the device details for the Device from which when I go to Google Play my App shows incompatible.
Motorola DROID Bionic
Android Vs 4.0.4
Verizon Wireless CDMA
System Version 6.7.230.XT875.Verizon.en.US (Leaked ICS Build for DROID Bionic)
Build Number 6.7.2-223
I have tried turning Copy Protection On/Off from Google Play but same result.
I am unable figure out what is causing this incompatibility with my app and device because Google Play Publishing shows this Device is supported by my release apk.
Is there any chance that me using a leaked ICS build for the Bionic has anything to do with it? It would be very helpful if anyone with 4.0.4 or (Android device running any version of ICS) can try to download the app from Google Play and see if the App is incompatible with their device too or its just me. Other than that suggestions on a way to fix this would be tremendously helpful.
Thanks so much.
Update: I am using two SDKs with my App - Flurry SDK and Skyhook Wireless SDK jar files both of which are compatible with Android 4.0. Also I have added Android Support Library and compiled the codebase against Android 4.0.3 and the App still is incompatible with the device and build mentioned above running Android v 4.0.4
Problem Solved!
First of all there is nothing wrong in the Manifest or the version of Android SDK I compiled the code base against which is Android 4.1.
I could search for and install the App when I turned Copy Protection OFF from Google Play developer console and waited 30 minutes to 1 hour for the new copy protection setting to take effect. The key here is that after changing the Copy Protection settings you have to wait. This does not take effect immediately.
Previously Copy Protection was ON for Tooyoou and after I wrote to Android developer support I got the clue in their reply email as below.
If your app no longer appears in Google Play after enabling Copy Protection, please note that our copy protection relies on being able to trust the build of Android that the app is installed on. Therefore, we only show copy-protected apps to known good builds of Android. If a specific port of Android is not a known good build (e.g. some “Custom ROMs”) or the device is rooted, Google Play will not display copy-protected apps to these devices. If the users switch to an official version of Android, they'll be able to see your application again.
Since I am running a custom unreleased ROM on my DROID BIONIC this is what caused the issue. Stock ASOP ICS and Jelly Bean devices were able to download and install the app even when Copy Protection was ON. Copy Protection is a bit tricky for Paid App but since Tooyoou is free there is not much to care about.
Also note Copy Protection is supposedly being deprecated soon and Licensing feature in the Android SDK is the way to go for Paid App copy protection.
have you tried adding android:xlargeScreens="true" to support-screens?