Currently we are using Android emulator by Android Studio along with Katalon. Most of the time the app crashes. We are looking to buy Genymotion but before that we want to make sure it works with Katalon. When I googled it, I saw a old post on 2018 that Katalon won't support Genymotion. What about now?
I haven't tried Katalon Studio yet, but Genymotion Desktop virtual devices usually show up as real devices to other tools. So it should work.
The easiest way to make sure it works for you is to give a try. For the best performances, you can download the latest beta from https://www.genymotion.com/download-beta/.
Related
a bit of a reverse question.... We're looking to develop apps using vs 2017 and Xamarin. However, we simply can't get the Android emulator to work with a usb webcam on a windows 10 PC.
We've just running the emulator, no visual studio code and using the camera app on the emulator. We've tried all the different version of the OS, all have the same result... If we set the front or back camera to emulate, we see the black and white checkerboard but if we set it to webcam(0), we get a could not connect to camera error msg.
We have also tried all the suggestions in similar questions, i.e. clear the memory, increasing sdcard.size etc.
Android studio's emulator has an error "can't connect to camera"
Android Emulator unable to open/connect with real webcam
Nothing seems to work...and none of the above answers have a positive answer (other than use a different emulator, which we are about to try)
So my question is "has anybody ever got this to work" or we hunting for a unicorn and it just doesn't work?
Well to be honest, the unicorn was there the first time I connected my cheap Genius USB camera from 2007 into my Windows 8.1 PC and configured the Back Camera as Webcam(0) in the Android emulator, to test a barcode scanning app made with Cordova 7.1.0 CLI.
I would suggest you to try with Android system images from different API levels (I think I used Android 5.1 or 6.0 for my tests) and also, why not, update the Android SDK tools. (I used the old SDK tools 24 at the time). If using the standalone SDK manager instead of Android Studio (like I do) follow these steps to update your SDK tools to version 27.
I hope this helps, anyway, you now know that the unicorn may be elusive but it can be found if you have the proper settings.
I'm having trouble getting any android emulator other than "Xamarin Android Player" to work (only with older versions of android).
What kind of virtual device/settings/properties should I use so that I can test newer versions of android and not have to wait 15 minutes for the emulator to startup?
is there a "Go-to" virtual device/emulator setup that doesn't take 15+ minutes to load?
(using windows 10/Visual Studio 17/2015)
The Xamarin android player has been discontinued for a while. As a visual studio user you should probably be moving onto the Visual Studio Android Emulator. There is a guide here on setup
https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/
it is also available with visual studio 2017, and if i remember correctly is an option available in the Vs2017 installer.
I highly suggest Genymotion for most uses. You can download the free version which works well for most basic things (there are also a few small things you can do using the adb command prompt without having to buy the full version, such as taking screenshots).
Link to free version
They have a good list of different devices. I have also recently even got it successfully connecting to my Parallels Windows machine while the emulator is running on my Mac. Let me know if you need help with this specific scenario.
The other option for you is the Visual Studio Android Emulator. When it first cam out I tried using it but was not able to because I would need to run it on a Parallels VM which does not allow nested virtualization.
I know that Android studio comes with an Emulator for testing apps. but this Emulator is too damn slow and never runs on my machine.
so i was checking for alternatives like if at all there is a standalone emulator which i can install on my system and upload my APKs and test. It is good if this emulator tool kit also shows the logs.
I just want something to test my Apps without the Emulator that comes with Android SDK.
While i was browsing SO i bumped into this here check for the comment that Paul Ratazzi has written, (second comment) this one is a paid solution so i did not dig into it much.
Genymotion is free for individuals. So you can use it unless its commercials and better than Emulators.
I'm using Xamarin Studio and Xamarin Android Player on my windows 10 PC.
I'm having trouble starting Lollipop/Marshmallow (API 21/23) devices using the XAP, but on the other hand, launching Kitkat (API 19) works prefectly.
I've downloaded the required android SDK, tried reinstalling everything again and again but nothing works.
It seems wired, because it is not a problem with Virtual Box, nor with my PC or my XAP installation (if it was, than why Kitkat works?).
I've tried every solution I could possibly find, but nothing works.
Any ideas on what could cause this problem?( If further information is required, I will be happy to add :)
EDIT
It does not matter whether I start the devices through VS/XS/XAP. It all comes down to the same problem, but for the sake of simplicity, let's say I'm running them directly through XAP. Here is a screen shot of what happens when I launch Lollipop (which is API 22, and not 21, for a strange reason) :
For like 5 minutes, the following occur:
Than, forever:
And after a few hours it says booting or something like that, and than restarts to the first position.
With Kitkat, it just starts :).
you probably missed the intel HAXM update.. may be a possible duplicate: Android 5.0 (API Level 21) AVD not launching Intel Atom x86_64
First off, it's difficult to determine the problem without more information. Please list or screenshot the build error(s) you receive when you try to debug your app on a XAP emulator.
But on a hunch... within the past week, I had a problem with similar symptoms. In my case, I had to update project packages in order for my Xamarin Forms project to run on the higher Android APIs.
Reference on how to update packages: https://developer.xamarin.com/guides/cross-platform/application_fundamentals/nuget_walkthrough/#Package_Updates
It might be that hyper-v is causing the problem: "VirtualBox and Hyper-V cannot co-exist on the same machine".
Try to disable it using bcedit as explained in the link.
For further reference, see this discussion
After launching xamarin android player, manually launch virtual box.
You should see the device listed on the left. There is a good chance it will say "stalled." If it says anything other than "Running," try reseting it or starting it.
I also had problems with XAP and my solution was to use Genymotion instead.
Did you try Genemotion
I think it is best Android emulator.
I would post a comment but my reputation is too low.
I don't know if this emulator works with Xamarin studio but if you use Visual Studio it may be an option for you.
Here is the solution:
I had the similar issue and fix the issue as follows.
delete the existing device simulator
reinstalled the simulator again
deploy the solution again.
I know I could use my Desire Z as a test phone, but what if I want to develop for 3.0 Honeycomb? What's an alternative for the emulator since it's so slow?
http://www.bluestacks.com/
This site has been getting some press recently. It seems that they are going to launch a windows runnable version of android later this year. This will be another alternative to using devices or emulators for testing I would imagine.
A general solution to the slowness of processor-emulation based emulators is to run a build of the embedded environment compiled for the same processor and general architecture as the hosting machine, in virtual machine software which can run most of the code native, and only has to trap and emulate privileged/hardware-related actions.
In other words, you run the x86 build of android in VirtualBox, vmware, or whatever, and dispense with the overhead of emulating an arm processor.
In quick web searching I'm not getting a confident answer if there's a working build of Honeycomb for x86 yet, but presumably there will be a build of that or a later android version at some point.
The only alternative is to have a physical device with Android 3.0 imaged on it.
Try this one for a change it actually provides an eclipse plugin and it uses cloud i guess it is faster than the emulator comes with android by default http://www.genymotion.com/features/