I have developed an Android app using Visual Studio 2019 and Xamarin Forms, all patched with the latest updates. For verification on an Android device, I purchased an Asus C214M Chromebook and published to it from within Visual Studio. To boost my confidence level, it published and ran both debug and release versions of my app.
In the process of publishing to Play Store, I added d8 as the dex compiler and release still runs on my Chromebook.Once it is published to Play Store it shows compatibility with 13,060 devices and there are no exclusions. When searching for Chromebook or Asus my device does not show up and no Chromebooks show as compatible.
Research and testing experience show that Xamarin apps are compatible with Chromebook, so what could I be missing in the manifest or compiler settings? The link is https://play.google.com/store/apps/details?id=com.linkemupllc.wetyourwhistel. Any suggestions?
Related
I've successfully upload android app based on xamarin forms in google play store, it shows the list of my real devices that are compatible but it also shows that all my emulators are not compatible with it. When I debug it from visual studio it runs on my emulator. Now that it's in google play I want to try it in my emulator since I don't currently have my physical device I can't install it due to compatibility. It says not compatible to Android SDK built for x86.
Using visual studio 15.7.4
Xamarin 4.10.10.2
Xamarin forms project
compile version api level 26
target android version api level 26
release mode
sdk link assemblies only
using Xamarin forms 3.1.0
Issue:
app starts fine (although long startup time) in debug mode. After installed to 2 different real phones the app splash screen shows on launch but hangs indefinitely
The solution for me was to enable "Zipalign" on the "Signing and aligning APK file(s)" task in my Xamarin Android build definition on Azure Devops (previously VSTS). I got the answer from here
This turned out to be something with the build definition in VSTS, as it worked when built right from Visual Studio
I was having trouble using the Android emulator in Visual Studio Community 2017 and I decided to create a blank project to see if it will run. I get this error message when attempting to run it in the Live Xamarin Player:
Starting Android Emulator Android_Accelerated_x86_Nougat...
Failed to boot Android device emulator-5554...
Unable to deploy to Android_Accelerated_x86_Nougat, please ensure the Xamarin
Live Player app is open and the device is on the same network as Visual Studio.
Why would I have trouble running the emulator in a fresh blank project when I didn't even write a single line of code? Thanks for your help.
UPDATE: So I installed the latest Android SDK 8.0 along with they system image and tried to create a virtual device that uses it. But the Android Virtual Device Manager shows a, 'No system images installed' message when I selected the 8.0 framework. So I installed an earlier version of the SDK along with a system image (5) and was able to create a virtual device with it. So another question is why wouldn't the system images show up for the 8.0 framework?
The $(TargetFrameworkVersion) for Xamarin.Forms.Platform.Android.dll
(vv8.0) is greater than the $(TargetFrameworkVersion) for your project
(v7.1). You need to increase the $(TargetFrameworkVersion) for your
project
This means the Xamarin.Forms library is targeting Android 8.0 (API level 26) but your project is setup for Android 7.1 (API level 25). You can't change the Xamarin.Forms target version without downgrading, but you can change your project target version easily. You can learn more about these concepts from Xamarin. Be aware some of the details of that Xamarin blog post are already out of date!
There is another nice blog post from Xamarin which can walk you through the process of setting your system up for Android 8.0 API level 26. It's normally not this complicated, but Google changed their SDK tools internally between 25 and 26 in very major ways. They changed from GUI tools to command line tools.
You'll probably also want to get the (in preview) Xamarin Android Device Manager if you don't have a physical device to test with. This Xamarin Android Device Manager tool is the only way to create and configure API 26 and higher emulators without using the Google command line tools.
It seems as though Google has gotten rid of the GUI apps that manage the SDK and Virtual Devices in the latest version, so when you try to create a new virtual device with 8.0 it's not compatible with the GUI tools. Until Xamarin releases a GUI tool to replace them we can use the command-line to manage the SDK and virtual devices.
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/sdk-cli-tooling-changes
https://developer.android.com/studio/command-line/avdmanager.html
I have downloaded latest Android Studio 2.2.3 and I want to start with C examples for project Tango phone (Lenovo Phab 2 Pro) using C API. The phone itself says it's run Android 6.0.1, kernel 3.10.84 on device.
Google developer documentation for Tango Project suggest to install Android Studio with Android SDK 24.4.1, Platform tools 23.1 and NDK 11.0.0.
By installing latest Android Studio there is no offering to install those versions of tools. Is it possible to use whatever SDK for development (latest)?
Where do I find aforementioned versions?
What Android SDK & NDK version is required for phone which run Android 6.0.1?
I started using the Dev Kit which runs Android 4.4 KitKat and I just recently got the Phab 2 Pro this week and I didn't need to make any updates to my Android Studio SDK manager.
Since I am working only with the Tango and not with the underlying Android features, I have found no need to require 6.0 for I am not using any of the extra features.
Also go here and clone the repo and run the hello-world and see if you can get it to work on your phone, if so you are good to go!
the SDK Manager which is part of Android Studio offers you choices on levels of android builds like 4.4.2/5.1/6.0/6.1, etc. Platform tools package is a module within the SDK Manager which also has levels which are based on the android build. The NDK is a completely different package and depending on what you want to accomplish you might be able to not worry about it to start of with. install Android Studio and then setup the SDK Manager to cover what devices you want to build for. get the latest Platform tools package setup and you will be ready to code. once you start setting up your environment things will fall in place. for the most part the installer does the work. pay attention to the things needed prior to installing Android Studio. i think you need to install a jdk and set paths and variables.
I am new to Xamarin Studio. I am trying to create an app for Android Wear using Xamarin studio. I have installed the Xamarin Studio 5.5 (upto date version) and Xamarin.Android version 4.18 (Trial Edition). I've gone through the below link before I start to set up my environment.
http://blog.xamarin.com/tips-for-your-first-android-wear-app/
As said in the blog, I have installed the latest Xamarin Studio, in which I couldn't find the template for creating a new Android Wear application in either my XamarinStudio or Visual Studio.
I have tried to download the sample given in the below link:
http://developer.xamarin.com/samples/android/Android%20Wear/
On building the samples, it gives me the dll missing errors.
for ex: I have downloaded the Eliza Chat sample from the above sample, and on running the sample I have been faced some dll missing issues. After downloading them manually from internet and refer them, I am facing the below error
"Error 1 No resource found that matches the given name: attr 'android:windowSwipeToDismiss'. C:\Users\XXX\AppData\Local\Xamarin\Android.Wearable\1.0.0\embedded.\res\values\values.xml 128 ElizaChat"
Note: I have installed the Android Wear Emulator with the help of the SDK Manager. And I have installed the Android L (API 20, L Preview) and Android 4.4 W(API20) through SDK Manager. And I have installed Android Support Repository and Android Support Library.
Do I need to install any thing else to work with Android Wear application. Any help would be appreciable.
Thanks,
Karuppasamy P