Develop Reference

Getting timeout on my OnePlus 5T while running Appium

I am using Appium version 1.15.0 and while running my Appium app automation suite on my OnePlus 5T, I am getting error : An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 5441 ms. Timing out.

Android Studio Emulator wont start

So everything was working fine, today I opened android studio and try to run the emulator, and it wont start. I will provide the errors in an image bellow.
I tried wiping the emulators data , and disabled the antivirus, I tried new device...
Please help I need it :(
ERRORS OF EMULATOR PICTURE
11:45 AM Gradle sync started
11:45 AM Gradle sync finished in 2 s 250 ms (from cached state)
11:46 AM Executing tasks: [clean, :app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 47 s 998 ms
11:47 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 20 s 141 ms
11:48 AM Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: C:\Users\User.android\emulator-grpc.cer security will be disabled.
11:48 AM Emulator: Started GRPC server at 127.0.0.1:8554
11:48 AM Emulator: C:\Users\User\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
11:48 AM Emulator: deleteSnapshot: for default_boot
11:48 AM Emulator: Process finished with exit code 0
11:49 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:49 AM Gradle build finished in 5 s 906 ms

Possible solutions
Invalidate/Restart Android studio
Open AVD Manager select you emulator and wipe Data from the dropdown
Installing Intel latest Intel HAXM
or delete current emulator and install new one

I want to say, that any possible solution did not work for me, I lost 4 hours working on that. I quit and installed Genymotion , I can tell that it runned smoother than the android emulator.

Appium: custom android app keeps crashing on launch

Have a problem where all of a sudden a previously working appium based android app selenium test has stopped working as it did (consistently successful).
The issue is specifically to do with the launch of the app by appium (the app always launches when opened with physical user input..). Basically the app launches, the loading screen appears and then it crashes. This happens most of the time but not always. I've found it usually works fine initially after restarting the phone. However, it'll crash on subsequent runs.
Any assistance would be much appreciated. Tried many things/searching online already but it's all been to of no avail..
Here's the appium output:
[AndroidDriver] Parsed pid: '27608' pkg: 'com.dedsert.betbright.uat' from
[AndroidDriver] USER PID PPID VSIZE RSS WCHAN PC NAME
[AndroidDriver] u0_a236 27608 4736 3621124 393160 0 0000000000 R com.dedsert.betbright.uat
[AndroidDriver] Returning process name: 'com.dedsert.betbright.uat'
[AndroidDriver] Found webviews: ["WEBVIEW_com.dedsert.betbright.uat"]
[AndroidDriver] Available contexts: ["NATIVE_APP","WEBVIEW_com.dedsert.betbright.uat"]
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/a9457315-d657-4fd1-bdf0-36fe5d76b3c5/context 200 245 ms - 76
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_RESULT: shortMsg=java.lang.StackOverflowError
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_RESULT: longMsg=stack size 1037KB
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_CODE: 0
[UiAutomator] UiAutomator exited unexpectedly with code 4294967295, signal null
[UiAutomator] Moving to state 'stopped'
[AndroidDriver] Shutting down Android driver
[Appium] Closing session, cause was 'UiAUtomator shut down unexpectedly'
[Appium] Removing session a9457315-d657-4fd1-bdf0-36fe5d76b3c5 from our master session list
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\kroring\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","ce051715c336451002","shell","am","force-stop","com.dedsert.betbright.uat"]
[ADB] Pressing the HOME button
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\kroring\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","ce051715c336451002","shell","input","keyevent",3]
[AndroidBootstrap] Cannot shut down Android bootstrap; it has already shut down
[Logcat] Stopping logcat capture
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\kroring\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","ce051715c336451002","shell","am","force-stop","io.appium.unlock"]
[AndroidDriver] Not cleaning generated files. Add `clearSystemFiles` capability if wanted.
[HTTP] --> POST /wd/hub/session/a9457315-d657-4fd1-bdf0-36fe5d76b3c5/context {"name":"WEBVIEW_com.dedsert.betbright.uat"}
[HTTP] <-- POST /wd/hub/session/a9457315-d657-4fd1-bdf0-36fe5d76b3c5/context 404 1 ms - 131
Not a whole lot to be seen on the IntelliJ side - did spot this in the stacktrace given:
org.openqa.selenium.remote.SessionNotFoundException: A session is either terminated or not started (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 5 milliseconds

Uninstall appium and reinstall appium and it will work for you.
From command line.
npm uninstall -g appium
Reinstall the appium.
npm install -g appium

Looks like your phone is out of memory. It could be worthwhile to clear the cache of your testing phone :
Power off your device. This method is different for different
manufacturers, and you should look it up on the internet before
proceeding further.
Load into your bootloader screen by holding down
a combination of keys. In some devices, you have to press the Power
button with Volume down key simultaneously. In other devices, Power
button with both the Volume keys have to pressed simultaneously.
Touchscreen might not work, and you have to navigate using Volume
keys.
Go to Recovery and select it with a tap on the Power button.
Go to Wipe cache partition and tap the Power button to select it.
After the cache gets cleared, select Reboot system now.
Information from (step 4): https://fossbytes.com/clear-android-cache-data-quick-methods/

Error While Launching AVD in Android studio

Please help I am getting the following error While launching AVD
Cannot launch AVD in emulator.
Output:
emulator: WARNING: VM heap size set below hardware specified minimum of 256MB
Warning: requested ram_size 1536M too big, reduced to 512M
emulator: WARNING: Setting VM heap size to 384MB
WARNING: unable to configure any DNS servers, name resolution will not work
Hax is enabled
Hax ram_size 0x20000000
HAX is working and emulator runs in fast virt mode.
console on port 5554, ADB on port 5555
emulator: emulator window was out of view and was recentered
emulator: WARNING: UpdateCheck: Failure: Error
emulator: WARNING: UpdateCheck: failed to get the latest version, skipping check (current version '25.1.7'
Cannot launch AVD in emulator.
Output:
emulator: WARNING: VM heap size set below hardware specified minimum of 256MB
Warning: requested ram_size 1536M too big, reduced to 512M
emulator: WARNING: Setting VM heap size to 384MB
WARNING: unable to configure any DNS servers, name resolution will not work
Hax is enabled
Hax ram_size 0x20000000
HAX is working and emulator runs in fast virt mode.
console on port 5554, ADB on port 5555
emulator: emulator window was out of view and was recentered
emulator: WARNING: UpdateCheck: Failure: Error
emulator: WARNING: UpdateCheck: failed to get the latest version, skipping check (current version '25.1.7'
screenshot of error

How much RAM did you configure HAXM for when it installed? If you installed HAXM to use 512M, then your AVD isn't going to be able to use more than that.
I'd try installing it again: https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x

Problems launching Android java project in a Android Virtual Machine using Eclipse

I have installed and set up Eclipse and the plugin ADT in order to work with Android SDK. So far so good. But when I try to launch a VM(virtual Machine) for any android platform that I choose (for example: android 3.2) I just get the skin launched together with a keyboard console and phone buttons, it seems to boot up to a state and then does nothing but displays the android logo on the main vm screen and that's all it does - no more!, no VM functionality!, what's going on? Have I missed out some step? Please help...
Have been waiting sometimes over 10 mins in each case for the emulator to start.
I launched/ran an Android project test sample; 'hello world' from the eclipse environment after installing the ADT plugin for Android These are the error messages I had displayed in the console ddms:
[2012-04-30 14:31:20 - HelloAndroid]
[2012-04-30 14:31:20 - HelloAndroid] Android Launch!
[2012-04-30 14:31:20 - HelloAndroid] adb is running normally.
[2012-04-30 14:31:20
- HelloAndroid] Performing com.example.helloandroid.HelloAndroidActivity activity launch
[2012-04-30 14:31:20 - HelloAndroid] Automatic Target Mode: launching
new emulator with compatible AVD
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:20 -
HelloAndroid] Launching a new emulator with Virtual Device
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:40 -
Emulator] Warning: No DNS servers found
[2012-04-30 14:31:52 -
Emulator] emulator: emulator window was out of view and was recentered
[2012-04-30 14:31:52 - Emulator]
[2012-04-30 14:31:53 - HelloAndroid]
New emulator found: emulator-5554
[2012-04-30 14:31:53 - HelloAndroid]
Waiting for HOME ('android.process.acore') to be launched...
[2012-04-30 14:49:03 - HelloAndroid] HOME is up on device
'emulator-5554' [2012-04-30 14:49:03 - HelloAndroid] Uploading
HelloAndroid.apk onto device 'emulator-5554'
[2012-04-30 14:49:03 -
HelloAndroid] Installing HelloAndroid.apk...
[2012-04-30 14:51:38 -
HelloAndroid] Failed to install HelloAndroid.apk on device
'emulator-5554!
[2012-04-30 14:51:38 - HelloAndroid] (null)
[2012-04-30 14:51:39 - HelloAndroid] Launch canceled!
At no point have I have anything but the Android logo displayed on my emulator. I have tried various platform emulators - none of them are performing!
A second lot of errors I received back on a test run after I checked the user data wiped in the Run configuration menu was: result
: [2012-04-30 17:20:27 - Emulator] Failed to allocate memory: 1455
[2012-04-30 17:20:27 - Emulator]
[2012-04-30 17:20:27 - Emulator] This
application has requested the Runtime to terminate it in an unusual
way.
[2012-04-30 17:20:27 - Emulator] Please contact the application's
support team for more information.
Bench mark results of my computer using Novabench incase anyone wants to check, are:
30/04/2012 17:45:59 Microsoft Windows 7 Starter Intel Atom N550
1.50GHz # 1500 MHz Graphics Card: Intel(R) Graphics Media Accelerator 3150
1014 MB System RAM (Score: 78) - RAM Speed: 1610 MB/s
CPU Tests (Score: 70) - Floating Point Operations/Second: 24110532 -
Integer Operations/Second: 43813828 - MD5 Hashes Generated/Second:
159380
Graphics Tests (Score: 1) - 3D Frames Per Second: 3
Hardware Tests (Score: 6) - Primary Partition Capacity: 87 GB - Drive
Write Speed: 14 MB/s

Do you Run your project or only start an emulator? After starting emulator, click Run button and select "Run as Android project".

I am not sure how long you waited, but starting the emulator the first time (before you have a snapshot) can take quite a long time. Depending on you hardware it can take more than 10 minutes to launch.

I had a similar issue which was solved by creating a new emulator and running it. You can check progress in Devices view through DDMS. Sometimes, this problem may occur when a snapshot enabled emulator hangs because of error, which can be solved by starting the emulator with user data wiped.

Emulator thread automatically cuts off if for some time you have not done any activity on it..
so.. keep running your app to keep emulator on LIVE!
My advice - if you having an android phone.. please usb debug it and Debug your application on your phone... You will feel relieved from the long durations of the emulator........ to run!! :)