I've been running my iOS appium tests using the Appium.app without issue.
I want to try using node + appium package instead but I'm running into the error displayed below.
I've tried reinstalling node and the appium and wd packages but the issue still persists. I've allowed OSX to accept incoming connections from node as well.
No issues found with my environment using: appium-doctor --ios
Appium log:
[Appium] Welcome to Appium v1.5.1 (REV c330ee9862bbc0db7d604e3b395cd1226417a9b9)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session {"desiredCapabilities":{"platformName":"iOS","platformVersion":"9.3","deviceName":"iPhone 6s","app":"/Users/User/Downloads/AppToTestSimulator.app (5).zip","autoAcceptAlerts":"false","appium_version":"1.5.1"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"platformName":"iOS","platformVersion":"9.3","deviceName":"iPhone 6s","app":"/Users/User/Downloads/AppToTestSimulator.app (5).zip","aut...
[Appium] Creating new IosDriver session
[Appium] Capabilities:
[Appium] platformName: 'iOS'
[Appium] platformVersion: '9.3'
[Appium] deviceName: 'iPhone 6s'
[Appium] app: '/Users/User/Downloads/AppToTestSimulator.app (5).zip'
[Appium] autoAcceptAlerts: 'false'
[Appium] appium_version: '1.5.1'
[BaseDriver] Capability 'autoAcceptAlerts' changed from string to boolean. This may cause unexpected behavior
[BaseDriver] The following capabilities were provided, but are not recognized by appium: appium_version.
[BaseDriver] Session created with session id: bc760657-425f-4b2a-a6a7-b0e96b3f7c01
[debug] [iOS] Not auto-detecting udid.
[BaseDriver] Using local app '/Users/User/Downloads/AppToTestSimulator.app (5).zip'
[debug] [BaseDriver] Copying local zip to tmp dir
[debug] [BaseDriver] Unzipping /var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/2016312-21862-1sug2zc/appium-app.zip
[debug] [BaseDriver] Testing zip archive: /var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/2016312-21862-1sug2zc/appium-app.zip
[BaseDriver] Unzipped local app to '/var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/2016312-21862-1sug2zc/AppToTest.app'
[debug] [iOS] Removing any remaining instruments sockets
[debug] [iOS] Cleaned up instruments socket /var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/instruments_sock
[debug] [iOS] Setting Xcode version
[debug] [iOS] Xcode version set to 7.3
[debug] [iOS] Setting iOS SDK Version
[debug] [iOS] iOS SDK Version set to 9.3
[debug] [iOS] Checking whether instruments supports our device string
[debug] [Instruments] Getting list of devices instruments supports
[debug] [Instruments] Instruments is at: /Applications/Xcode.app/Contents/Developer/usr/bin/instruments
[debug] [Instruments] Available devices: Apple TV 1080p (9.2) [A350CABB-DB34-4933-8C8D-94BE4E695BD9] (Simulator),iPad 2 (8.4) [8FF96C8F-5BAB-4863-945C-62C92F9F7C91] (Simulator),iPad 2 (9.3) [74017AF7-1E44-4708-BA84-3BD09E5A50AD] (Simulator),iPad Air (8.4) [018AD91A-560B-475B-8E59-4633D4E4F70F] (Simulator),iPad Air (9.3) [441357FB-6D52-41E4-8AA3-682BE3A1CA03] (Simulator),iPad Air 2 (9.3) [5D925D0C-7FA2-4CEE-BE47-85E0DACFA67A] (Simulator),iPad Pro (9.3) [BADE2306-4190-44F8-A88A-21BC19137589] (Simulator),iPad Retina (8.4) [6436FE08-5493-4E95-9AB0-8CDB5EB14FC9] (Simulator),iPad Retina (9.3) [EDDB468C-EA62-443F-B273-FEC00F96FA6B] (Simulator),iPhone 4s (8.4) [DA7DF90E-7EB9-4199-ABE8-1DF2B89C593B] (Simulator),iPhone 4s (9.3) [64305631-8F8E-4DFF-BF10-6254B30C885A] (Simulator),iPhone 5 (8.4) [A2E02B24-E960-4182-8B1D-5EE633E64E4D] (Simulator),iPhone 5 (9.3) [3610DBC3-1F8E-48F3-8E86-93E2DCD28B3C] (Simulator),iPhone 5s (8.4) [385EBC18-FBEE-43D3-8A9F-ED6FB9E17D99] (Simulator),iPhone 5s (9.3) [1177F60B-F9A5-4D6E-B9E7-00F172ECB09C] (Simulator),iPhone 6 (8.4) [1CB02197-3B62-444F-B745-11884344D226] (Simulator),iPhone 6 (9.3) [F05E7BCD-1A83-4F64-8C43-9D6320116780] (Simulator),iPhone 6 Plus (8.4) [4683EB66-6644-4D3B-997B-6A417C9C7C5C] (Simulator),iPhone 6 Plus (9.3) [72630DFB-B5B1-4D79-B7C3-DAF39E1EE0F6] (Simulator),iPhone 6s (9.3) [4116EA28-E0C2-45F2-A201-22C3B1CAFBE3] (Simulator),iPhone 6s (9.3) + Apple Watch - 38mm (2.2) [D8DD477B-D5C4-4575-A83B-C5D95D40A1E1] (Simulator),iPhone 6s Plus (9.3) [7716603A-2DAE-439D-A59A-AA561C90D888] (Simulator),iPhone 6s Plus (9.3) + Apple Watch - 42mm (2.2) [A4FE07E7-4CC4-4507-AE70-E07B7EC0DE21] (Simulator)
[iOSSim] Retrieving device name string for Xcode version 7.3
[debug] [iOSSim] Getting device string from options: {"deviceName":"iPhone 6s","platformVersion":"9.3","forceIphone":false,"forceIpad":false}
[debug] [iOSSim] Fixing device. Changed from 'iPhone 6s' to 'iPhone 6s (9.3) ['
[debug] [iOSSim] Final device string is 'iPhone 6s (9.3) ['
[debug] [iOS] iOS sim UDID is 4116EA28-E0C2-45F2-A201-22C3B1CAFBE3
[iOSSim] Constructing iOS simulator for Xcode version 7.3
[debug] [iOS] No language specified. Using default strings
[debug] [iOS] Strings file not found. Looking in 'en.lproj' directory
[iOS] Could not file localizable strings file 'Localizable.strings'!
[debug] [ios-app-utils] Getting bundle ID from app
[iOS] Extracted bundleID: us.AppToTest.AppToTestPreprod from app: /var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/2016312-21862-1sug2zc/AppToTest.app
[debug] [iOS] Creating instruments
[debug] [UIAuto] Preparing bootstrap code
[debug] [UIAuto] Dynamic bootstrap dir: /Users/User/Library/Application Support/appium/bootstrap
[debug] [UIAuto] Dynamic env: {"nodePath":"/usr/local/bin/node","commandProxyClientPath":"/usr/local/lib/node_modules/appium/node_modules/appium-ios-driver/node_modules/appium-uiauto/build/lib/bin/command-proxy-client.js","instrumentsSock":"/var/folders/6v/w_s4j0fj27b1lnk8rnj0k4thvgjb4k/T/instruments_sock","interKeyDelay":null,"justLoopInfinitely":false,"autoAcceptAlerts":false,"autoDismissAlerts":false,"sendKeyStrategy":"oneByOne"}
...bug] [UIAuto] Dynamic bootstrap code: // This file is automatically generated. Do not manually modify!
[debug] [UIAuto] Dynamic bootstrap path: /Users/User/Library/Application Support/appium/bootstrap/bootstrap-f8e8ef362019f9d8.js
[debug] [UIAuto] Reusing dynamic bootstrap: /Users/User/Library/Application Support/appium/bootstrap/bootstrap-f8e8ef362019f9d8.js
[debug] [iOS] User specified default device, letting instruments launch it
[debug] [iOS] Running ios sim reset flow
[debug] [iOS] Killing the simulator
[debug] [iOSSim] Killing all iOS Simulators
[MJSONWP] Encountered internal error running command: Error: Condition unmet after 60011 ms. Timing out.
at spin$ (lib/asyncbox.js:118:13)
at tryCatch (/usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/regenerator/runtime.js:294:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/regenerator/runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/regenerator/runtime.js:136:37)
at run (/usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:89:39)
at /usr/local/lib/node_modules/appium/node_modules/asyncbox/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:100:28
at nextTickCallbackWith0Args (node.js:420:9)
at process._tickCallback (node.js:349:13)
[HTTP] <-- POST /wd/hub/session 500 62780 ms - 180
I resolved the issue by reinstalling x-code and performing the 'sudo authorize-ios' command. The latter was probably the only thing that was required.
Related
How do I get Android Studio virtual devices to run (stop terminating)?
Android Studio Chipmunk (2021.2.1)
This is the first time using Android Studio for me and I'm trying to get the Android emulator to work, to start learning Java. Everytime I try to run an emulator I get the following message:
The emulator process for AVD {device-name} has terminated.
I feel like I've tried everything I could find on the web. Here's what I have tried so far:
Checking my disk space as suggested here and even removing some unnecessary applications, despite having more than enough disk space (well over 80 GB).
Removing every virtual device and re-installing them again one by one using the built in Device Manager.
Removing the Android Emulator entirely and re-installing it from within the SDK Tools tab, found under the Tools > SDK Manager application menu.
Creating an advancedFeatures.ini file under C:\Users\ {name}\ .android\ as suggested here and in other posts with different lines in the file.
Restarting my PC and Android Studio throughout the entire process, after every step mentioned here.
Removing Android Studio completely from my system, then downloading it (from the official website) and installing it again.
Looking at the idea.log file. There's a bunch of errors regarding the emulator, which I cannot make sense of.
Does anybody have an idea what to do?
Here's what the idea.log file says about the emulator:
2022-05-16 10:23:53,804 [ 308433] WARN - alytics.SystemInfoStatsMonitor - CpuInfoFlags.fromExitCode(): unknown flag values '0x80'
2022-05-16 10:24:46,048 [ 360677] INFO - Emulator: Pixel 5 API Tiramisu - C:\Users\{username}\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Pixel_5_API_Tiramisu -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-05-16 10:24:47,098 [ 361727] INFO - Emulator: Pixel 5 API Tiramisu - C:\Users\{username}\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Pixel_5_API_Tiramisu -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-05-16 10:24:49,548 [ 364177] WARN - Emulator: Pixel 5 API Tiramisu - unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-05-16 10:24:49,564 [ 364193] INFO - Emulator: Pixel 5 API Tiramisu - Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release.
2022-05-16 10:24:49,564 [ 364193] WARN - Emulator: Pixel 5 API Tiramisu - Not all modern X86 virtualization features supported, which introduces problems with slowdown when running Android on multicore vCPUs. Setting AVD to run with 1 vCPU core only.
2022-05-16 10:24:51,046 [ 365675] WARN - Emulator: Pixel 5 API Tiramisu - cannot add library vulkan-1.dll: failed
2022-05-16 10:24:51,046 [ 365675] WARN - Emulator: Pixel 5 API Tiramisu - cannot add library vulkan-1.dll: failed
2022-05-16 10:24:51,073 [ 365702] INFO - Emulator: Pixel 5 API Tiramisu - configAndStartRenderer: setting vsync to 60 hz
2022-05-16 10:24:51,073 [ 365702] INFO - Emulator: Pixel 5 API Tiramisu - Sending adb public key [QAAAAC03lzdbz2r7trf4HeurXGQ9LdN2Kex6Luf2QjY0wlgNvxm+NCxU0TyJXB+NOfqXcglhbuChvc1zyLz57tbnSrH5zzmXMzN4WmbS9BTW5uIuNfLGP+TQRdHvBiWvqgkOSOKqp4NQiclDOfet4EuGUqRvxGuKbEYLWMsVHfMnXWSOuuUr5hQl1s/MPKkthtC0fVTDJMQIV5xAN85Z9pUhUqOdxPyU4X8xvo/nFFOaZLD4h+UyKp4Yn6WXvm+Q0aceAr2YvEirpBUbj2KFoMzFP29kokuZTmtENhEF/WQXjQ8OhecQ99z3NUQdIhWDk3x8xKvkWepxWCtKVGn3jCJObE8c4bGt2OUmsWQkvVP/9/5wh+B0qLTtInXtoQiNman64QEvrZMYOPZxIJ+RNBExu5pJytEK5ntxQhQPUcL3aY+mNNCQotGXyJrxPIvtiEJyUFHfQcM+Ulned9eDGTNN0TcOOWjBcKUoMt9NllZ5/mUCSsf0rgyy4YvtLiqV/1EWxYo96kl+v8MH6jMiJN9MHgzPFZMt8+azTZGDoDIbo7T5aBvv3hvECUCiWwIdbhQmK6bKdNqjd8ovnF0hAcporw0iPC+mNWiC9onVToMgJE7oRwtCi42voElCDTl/+cuEVnBREVjk16I31fuWIewM6pBoSM7F3wwPbjRXbsedpuQ613f+HwEAAQA= #unknown]
2022-05-16 10:24:51,074 [ 365703] INFO - Emulator: Pixel 5 API Tiramisu - added library C:\Users\{username}\AppData\Local\Android\Sdk\emulator\lib64\vulkan\vulkan-1.dll
2022-05-16 10:24:51,074 [ 365703] INFO - Emulator: Pixel 5 API Tiramisu - Rootcanal has been activated.
2022-05-16 10:24:51,074 [ 365703] INFO - Emulator: Pixel 5 API Tiramisu - HAX is working and emulator runs in fast virt mode.
2022-05-16 10:24:51,508 [ 366137] INFO - b.PhysicalDeviceChangeListener - emulator-5554 connected
2022-05-16 10:24:51,510 [ 366139] INFO - Emulator: Pixel 5 API Tiramisu - Started GRPC server at 127.0.0.1:8554, security: Local+token
2022-05-16 10:24:51,511 [ 366140] INFO - Emulator: Pixel 5 API Tiramisu - Advertising in: C:\Users\{username}\AppData\Local\Temp\avd\running\pid_3028.ini
2022-05-16 10:24:51,915 [ 366544] INFO - Emulator: Pixel 5 API Tiramisu - VCPU shutdown request
2022-05-16 10:24:51,915 [ 366544] INFO - Emulator: Pixel 5 API Tiramisu - Deleting snapshot default_boot
2022-05-16 10:24:52,061 [ 366690] INFO - Emulator: Pixel 5 API Tiramisu - Shutting down gRPC endpoint
2022-05-16 10:24:52,062 [ 366691] INFO - Emulator: Pixel 5 API Tiramisu - Shutting down gRPC endpoint
2022-05-16 10:24:52,074 [ 366703] INFO - Emulator: Pixel 5 API Tiramisu - Closing down rootcanal.
2022-05-16 10:24:52,473 [ 367102] ERROR - Emulator: Pixel 5 API Tiramisu - Running multiple emulators with the same AVD
2022-05-16 10:24:52,474 [ 367103] ERROR - Emulator: Pixel 5 API Tiramisu - Android Studio Chipmunk | 2021.2.1 Build #AI-212.5712.43.2112.8512546
2022-05-16 10:24:52,485 [ 367114] ERROR - Emulator: Pixel 5 API Tiramisu - JDK: 11.0.12; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-05-16 10:24:52,486 [ 367115] ERROR - Emulator: Pixel 5 API Tiramisu - OS: Windows 10
2022-05-16 10:24:52,487 [ 367116] ERROR - Emulator: Pixel 5 API Tiramisu - Last Action:
2022-05-16 10:24:52,487 [ 367116] ERROR - Emulator: Pixel 5 API Tiramisu - is an experimental feature.
2022-05-16 10:24:52,487 [ 367116] ERROR - Emulator: Pixel 5 API Tiramisu - Android Studio Chipmunk | 2021.2.1 Build #AI-212.5712.43.2112.8512546
2022-05-16 10:24:52,487 [ 367116] ERROR - Emulator: Pixel 5 API Tiramisu - JDK: 11.0.12; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-05-16 10:24:52,488 [ 367117] ERROR - Emulator: Pixel 5 API Tiramisu - OS: Windows 10
2022-05-16 10:24:52,488 [ 367117] ERROR - Emulator: Pixel 5 API Tiramisu - Last Action:
2022-05-16 10:24:52,488 [ 367117] ERROR - Emulator: Pixel 5 API Tiramisu - Please use -read-only flag to enable this feature.
2022-05-16 10:24:52,489 [ 367118] ERROR - Emulator: Pixel 5 API Tiramisu - Android Studio Chipmunk | 2021.2.1 Build #AI-212.5712.43.2112.8512546
2022-05-16 10:24:52,489 [ 367118] ERROR - Emulator: Pixel 5 API Tiramisu - JDK: 11.0.12; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-05-16 10:24:52,489 [ 367118] ERROR - Emulator: Pixel 5 API Tiramisu - OS: Windows 10
2022-05-16 10:24:52,490 [ 367119] ERROR - Emulator: Pixel 5 API Tiramisu - Last Action:
2022-05-16 10:24:52,491 [ 367120] INFO - Emulator: Pixel 5 API Tiramisu - Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
2022-05-16 10:24:52,588 [ 367217] INFO - Emulator: Pixel 5 API Tiramisu - Process finished with exit code 1
2022-05-16 10:24:52,588 [ 367217] ERROR - Emulator: Pixel 5 API Tiramisu - Emulator terminated with exit code 1
java.lang.Throwable: Emulator terminated with exit code 1
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:182)
at com.android.tools.idea.avdmanager.EmulatorProcessHandler$ConsoleListener.onTextAvailable(EmulatorProcessHandler.kt:89)
at jdk.internal.reflect.GeneratedMethodAccessor62.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.intellij.execution.process.ProcessHandler$2.invoke(ProcessHandler.java:247)
at com.sun.proxy.$Proxy33.onTextAvailable(Unknown Source)
at com.intellij.execution.process.ProcessHandler.notifyTextAvailable(ProcessHandler.java:221)
at com.intellij.execution.process.ProcessTerminatedListener.processTerminated(ProcessTerminatedListener.java:54)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.intellij.execution.process.ProcessHandler$2.invoke(ProcessHandler.java:247)
at com.sun.proxy.$Proxy33.processTerminated(Unknown Source)
at com.intellij.execution.process.ProcessHandler.lambda$notifyTerminated$2(ProcessHandler.java:205)
at com.intellij.execution.process.ProcessHandler$TasksRunner.execute(ProcessHandler.java:280)
at com.intellij.execution.process.ProcessHandler.notifyTerminated(ProcessHandler.java:188)
at com.intellij.execution.process.ProcessHandler.notifyProcessTerminated(ProcessHandler.java:184)
at com.intellij.execution.process.BaseProcessHandler.onOSProcessTerminated(BaseProcessHandler.java:61)
at com.intellij.execution.process.BaseOSProcessHandler$1.lambda$startNotified$0(BaseOSProcessHandler.java:99)
at com.intellij.execution.process.ProcessWaitFor.lambda$new$0(ProcessWaitFor.java:45)
at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:213)
at com.intellij.execution.process.ProcessWaitFor.lambda$new$1(ProcessWaitFor.java:23)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:829)
2022-05-16 10:24:52,591 [ 367220] ERROR - Emulator: Pixel 5 API Tiramisu - Android Studio Chipmunk | 2021.2.1 Build #AI-212.5712.43.2112.8512546
2022-05-16 10:24:52,592 [ 367221] ERROR - Emulator: Pixel 5 API Tiramisu - JDK: 11.0.12; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-05-16 10:24:52,592 [ 367221] ERROR - Emulator: Pixel 5 API Tiramisu - OS: Windows 10
2022-05-16 10:24:52,593 [ 367222] ERROR - Emulator: Pixel 5 API Tiramisu - Last Action:
2022-05-16 10:24:53,887 [ 368516] INFO - Emulator: Pixel 5 API Tiramisu - Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
2022-05-16 10:24:53,950 [ 368579] INFO - Emulator: Pixel 5 API Tiramisu - Process finished with exit code 0
2022-05-16 10:24:54,122 [ 368751] INFO - b.PhysicalDeviceChangeListener - emulator-5554 disconnected
2022-05-16 10:25:38,691 [ 413320] INFO - rationStore.ComponentStoreImpl - Saving appClangTidySettings took 16 ms, NotificationConfiguration took 15 ms, YamlEditorOptions took 16 ms
2022-05-16 10:25:38,769 [ 413398] INFO - rationStore.ComponentStoreImpl - Saving Project(name=Learning_Environment, containerState=COMPONENT_CREATED, componentStore=C:\Users\{username}\AndroidStudioProjects\Learning_Environment)FileEditorManager took 15 ms, ServiceViewManager took 16 ms, Vcs.Log.Tabs.Properties took 16 ms, XDebuggerManager took 15 ms
Try to change the graphic of your emulator from automatic to Software
I don't know an exact cause of this problem - it seems something related to graphics, and happened after last emulator update in my case.
What helped me was running emulator using console and changing graphics settings. I'm using Ubuntu 20.04 so all paths are for linux.
List all your avds: $./emulator -list-avds
Then start avd with software acceleration mode: $./emulator -avd MY_AVD_NAME -gpu swiftshader_indirect - this very line started my avd. This is enough to use the emulator.
(Optional) I wanted to be able to start emulator from Android Studio, so tried different settings in avd, and what works was:
After this you can run your avd from AS or just with $./emulator -avd MY_AVD_NAME
Also it looks like there is an alternative way: change setting in /home/user/.android/avd/MY_AVD_NAME.avd/config.ini file:
hw.gpu.enabled = yes
hw.gpu.mode = swiftshader_indirect
Google link: https://developer.android.com/studio/run/emulator-acceleration#command-gpu
I am running Android Studio on Windows 8.1. When I try to run simple Hello World on a virtual device, it shows briefly then exits with dialog "The emulator process for AVD [device] has terminated.
Here is the output from the idea.log:
INFO - manager.EmulatorProcessHandler - Emulator: C:\Users\[my_username]\AppData\Local\Android\sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Nexus_4_API_22
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | encryption is off
INFO - manager.EmulatorProcessHandler - Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release.
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | Not all modern X86 virtualization features supported, which introduces problems with slowdown when running Android on multicore vCPUs. Setting AVD to run with 1 vCPU core only.
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library vulkan-1.dll: failed
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library vulkan-1.dll: failed
INFO - manager.EmulatorProcessHandler - Emulator: INFO | configAndStartRenderer: setting vsync to 60 hz
INFO - manager.EmulatorProcessHandler - Emulator: INFO | added library C:\Users\[my_username]\AppData\Local\Android\sdk\emulator\lib64\vulkan\vulkan-1.dll
INFO - manager.EmulatorProcessHandler - Emulator: HAX is working and emulator runs in fast virt mode.
INFO - b.PhysicalDeviceChangeListener - emulator-5554 connected
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Started GRPC server at 127.0.0.1:8554, security: Local
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Advertising in: C:\Users\[my_username]\AppData\Local\Temp\avd\running\pid_1072.ini
INFO - b.PhysicalDeviceChangeListener - emulator-5554 state changed to ONLINE
INFO - b.PhysicalDeviceChangeListener - emulator-5554 state changed to OFFLINE
WARN - #com.android.ddmlib - Failed to start monitoring emulator-5554
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Android emulator version 31.2.8.0 (build_id 8143646) (CL:N/A)
INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741819 (0xC0000005)
WARN - manager.EmulatorProcessHandler - Emulator terminated with exit code -1073741819
INFO - b.PhysicalDeviceChangeListener - emulator-5554 disconnected
However, I am able to run it from the command line successfully. The log is nearly identical:
I have searched these forums and tried everything:
Change Graphics Performance option to "Software"
Cold Boot Now option
Wipe Data option
Delete .android folder
Delete, create multiple different virtual devices
Run as Administrator
Install, reinstall Android Emulator
Increase IDE memory to max (2GB)
Reboot machine
I am out of ideas. Has anyone been able to solve this?
Android Studio Bumblebee | 2021.1.1 Patch 2
Build #AI-211.7628.21.2111.8193401, built on February 16, 2022
Runtime version: 11.0.11+9-b1341.60 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 8.1 6.3
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: mobi.hsz.idea.gitignore (4.1.0), org.intellij.plugins.markdown (211.7142.37)
Using Android Studio and when trying to run a simple demonstration app the emulator I selected starts up but never renders the app. In the event log I see stuff like the following:
2:59 PM Emulator: emulator: WARNING: Host CPU is missing the following
feature(s) required for x86 emulation: SSSE3
2:59 PM Emulator: Hardware-accelerated emulation may not work
properly!
2:59 PM Emulator: qemu-system-x86_64: warning: host doesn't support
requested feature: CPUID.01H:ECX.ssse3 [bit 9]
2:59 PM Emulator: qemu-system-x86_64: warning: host doesn't support
requested feature: CPUID.01H:ECX.sse4.1 [bit 19]
2:59 PM Emulator: qemu-system-x86_64: warning: host doesn't support
requested feature: CPUID.01H:ECX.sse4.2 [bit 20]
2:59 PM ADB rejected shell command (getprop): closed
2:59 PM Emulator: Process finished with exit code 0
Tried restarting Android Studio
Tried recreating the AVD image
Tried killing and restarting adb
Running Ubuntu 18.04 with Android Studio 3.4
I expected that the emulator would start up and render the app created so far. I'm following https://www.youtube.com/watch?v=dFlPARW5IX8 and at about 21:22.
It says to press play and the emulator should start and show the app we have coded so far. I never see this.
I am trying to configure Appium Grid with below node configuration.
-Hub is receiving proper capabilities from testng but hub is sending wrong capabilities to my only two nodes. (node configs are as follows )
Please do suggest where am I going wrong.
Emulator Node config
Command running the node with : node appium.js --port 4723 --nodeconfig G:\Selenium2\Grid\AppiumEmulatorNode.json
{
"capabilities": [{
"browserName": "Emulator_5.1.0",
"version": "5.1.0",
"maxInstances": 1,
"platform": "ANDROID"
}],
"configuration": {
"cleanUpCycle": 2000,
"timeout": 30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url": "http://192.168.0.104:4723/wd/hub",
"host": 192.168.0.104,
"port": 4723,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444 ,
"hubHost": "192.168.0.104"
}
}
Real device Node config
Command running the node with : node appium.js --port 4724 --nodeconfig G:\Selenium2\Grid\AppiumRealDevice.json
{
"capabilities": [{
"browserName": "Sony Xperia SP",
"version": "5.1.1",
"maxInstances": 1,
"platform": "ANDROID"
}],
"configuration": {
"cleanUpCycle": 2000,
"timeout": 30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url": "http://192.168.0.104:4724/wd/hub",
"host": "192.168.0.104",
"port": 4724,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444 ,
"hubHost": "192.168.0.104"
}
}
Testng file
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="TestsSuite" parallel="tests" thread-count="2" verbose="5">
<test name="Test1">
<parameter name="UdidOrDeviceName" value="YT910LQ91K"></parameter>
<parameter name="MobileVersion" value="5.2.0"></parameter>
<classes>
<class name="com.apps.AppiumTest.AppiumMessengerTest" />
</classes>
</test>
<test name="Test2">
<parameter name="UdidOrDeviceName" value="192.168.113.101:5555"></parameter>
<parameter name="MobileVersion" value="5.1.0"></parameter>
<classes>
<class name="com.apps.AppiumTest.AppiumMessengerTest" />
</classes>
</test>
</suite>
Grid hub Output
19:47:56.092 INFO - Registered a node http://192.168.0.104:4723
19:51:05.917 INFO - Registered a node http://192.168.0.104:4724
19:51:31.419 INFO - Got a request to create a new session: Capabilities [{appActivity=com.android.mms.ui.ConversationList, appPackage=com.android.mms, platformVersion=5.2.0, newCOmmandTimeout=1000, platformName=Android, deviceName=YT910LQ91K}]
19:51:31.433 INFO - Available nodes: [http://192.168.0.104:4723, http://192.168.0.104:4724]
19:51:31.438 INFO - Got a request to create a new session: Capabilities [{appActivity=com.android.mms.ui.ConversationList, appPackage=com.android.mms, platformVersion=5.1.0, newCOmmandTimeout=1000, platformName=Android, deviceName=192.168.113.101:5555}]
19:51:31.438 INFO - Trying to create a new session on node http://192.168.0.104:4723
19:51:31.460 INFO - Trying to create a new session on test slot {maxInstances=3, platformName=ANDROID, deviceName=192.168.113.101:5555, version=5.1.0}
19:51:31.476 INFO - Available nodes: [http://192.168.0.104:4724, http://192.168.0.104:4723]
19:51:31.486 INFO - Trying to create a new session on node http://192.168.0.104:4724
19:51:31.501 INFO - Trying to create a new session on test slot {browserName=Sony Xperia SP, maxInstances=1, version=5.1.1, platform=ANDROID}
Emulator Node output
This node receiving wrong set of data from Selenium Grid.It should receive emulator capabilities but it has received real device capabilities
C:\Program Files (x86)\Appium\node_modules\appium\bin>node appium.js --port 4723 --nodeconfig G:\Selenium2\Grid\AppiumEmulatorNode.json
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 0.0.0.0:4723
info: [debug] Non-default server args: {"nodeconfig":"G:\\Selenium2\\Grid\\AppiumEmulatorNode.json"}
info: Console LogLevel: debug
info: [debug] starting auto register thread for grid. Will try to register every 5000 ms.
info: [debug] Appium successfully registered with the grid on 192.168.0.104:4444
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 28.871 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 11.314 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> POST /wd/hub/session {"desiredCapabilities":{"appActivity":"com.android.mms.ui.ConversationList","appPackage":"com.android.mms","platformVersion":"5.2.0","newCOmmandTimeout":1000,"platformName":"Android","deviceName":"YT910LQ91K"}}
info: Client User-Agent string: Apache-HttpClient/4.5.1 (Java/1.8.0_65)
Real Device Node output
This node receiving wrong set of data from Selenium Grid.It should receive Real device capabilities but it has received emulator capabilities
C:\Program Files (x86)\Appium\node_modules\appium\bin>node appium.js --port 4724 --nodeconfig G:\Selenium2\Grid\AppiumRealDevice.json
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 0.0.0.0:4724
info: [debug] Non-default server args: {"port":4724,"nodeconfig":"G:\\Selenium2\\Grid\\AppiumRealDevice.json"}
info: Console LogLevel: debug
info: [debug] starting auto register thread for grid. Will try to register every 5000 ms.
info: [debug] Appium successfully registered with the grid on 192.168.0.104:4444
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 22.103 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 12.602 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 11.690 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 11.460 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: <-- GET /wd/hub/status 200 11.927 ms - 105 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}}}
info: --> POST /wd/hub/session {"desiredCapabilities":{"appActivity":"com.android.mms.ui.ConversationList","appPackage":"com.android.mms","platformVersion":"5.1.0","newCOmmandTimeout":1000,"platformName":"Android","deviceName":"192.168.113.101:5555"}}
info: Client User-Agent string: Apache-HttpClient/4.5.1 (Java/1.8.0_65)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : newCOmmandTimeout
info: [debug] Didn't get app but did get Android package, will attempt to launch it on the device
info: [debug] Creating new appium session 515cbed7-46c0-4fce-a2e0-652976c5a659
info: Starting android appium
info: [debug] Getting Java version
info: Java version is: 1.8.0_71
info: [debug] Checking whether adb is present
info: [debug] Using adb from C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe
warn: No app capability, can't parse package/activity
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it's already on the device
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices...
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe devices
info: [debug] 2 device(s) connected
info: Found device 192.168.113.101:5555
info: [debug] Setting device id to 192.168.113.101:5555
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 wait-for-device
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell "echo 'ready'"
info: [debug] Starting logcat capture
info: [debug] Getting device API level
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell "getprop ro.build.version.sdk"
info: [debug] Device is at API Level 22
info: Device API level is: 22
info: [debug] Extracting strings for language: default
info: [debug] Apk doesn't exist locally
info: [debug] Could not get strings, but it looks like we had an old strings file anyway, so ignoring
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell "rm -rf /data/local/tmp/strings.json"
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Skipping install since we launched with a package instead of an app path
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device...
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 push "C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
info: [debug] Pushing settings apk to device...
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 install "C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk"
info: [debug] Pushing unlock helper app to device...
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 install "C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
info: --> GET /wd/hub/status {}
info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}},"sessionId":"515cbed7-46c0-4fce-a2e0-652976c5a659"}
info: <-- GET /wd/hub/status 200 69.204 ms - 156 {"status":0,"value":{"build":{"version":"1.4.16","revision":"ae6877eff263066b26328d457bd285c0cc62430d"}},"sessionId":"515cbed7-46c0-4fce-a2e0-652976c5a659"}
info: Starting App
info: [debug] Attempting to kill all 'uiautomator' processes
info: [debug] Getting all processes with 'uiautomator'
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell "ps 'uiautomator'"
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.android.mms -e disableAndroidWatchers false
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_RESULT: shortMsg=java.lang.IllegalStateException
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_RESULT: longMsg=UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy#1034d97calready registered!
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_CODE: 0
info: [debug] UiAutomator exited
info: [debug] executing cmd: C:\Users\Harsha\AppData\Local\Android\sdk\platform-tools\adb.exe -s 192.168.113.101:5555 shell "echo 'ping'"
info: [debug] Attempting to uninstall app
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Cleaning up android objects
error: UiAutomator quit before it successfully launched
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: UiAutomator quit before it successfully launched
info: [debug] Error: UiAutomator quit before it successfully launched
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android.js:205:23)
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android-hybrid.js:249:5)
at Object.async.eachSeries (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:142:20)
at [object Object].androidHybrid.stopChromedriverProxies (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android-hybrid.js:233:9)
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android.js:200:10)
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android.js:222:9)
at [object Object].androidCommon.uninstallApp (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android-common.js:478:5)
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android.js:220:12)
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android.js:229:11)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:901:7
at [object Object].<anonymous> (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:180:9)
at ChildProcess.exithandler (child_process.js:194:7)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:818:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: UiAutomator quit before it successfully launched)","origValue":"UiAutomator quit before it successfully launched"},"sessionId":null}
Here's how the Grid decides to which node should a test be routed to.
It uses something called as a Capability Matcher, to help it decide as to which among its nodes should a test be routed to. If you don't provide a custom capability matcher [ You can take a look at this blog of mine to understand how to plugin in your own custom variant ], it resorts to relying on the DefaultCapabilityMatcher for doing this matching job.
Since you haven't set any of the attributes that the default capability matcher understands [ see here for learning what are those ], it always matches the first node with a test. That is why you are seeing the mess up.
It only understands browserName, platform, version and applicationName and for browserName, platform you cannot pass in any arbitrary values but can only use predefined values. See BrowserType and Platform java classes.
So to solve your problem, you have two options.
Option 1 : You build your own capability matcher which suites your needs (you can refer to my blog post link that I have shared above) and work with it.
Option 2 : You resort to using the capability "applicationName" wherein you provide a unique value to this for each of your nodes and then rely on your test to add this extra capability at the test level.
That should resolve your problem.
I was trying to test out a page of mine using Selenium and phpunit. I had coded it properly and tried it out on a Ubuntu 14.04 machine. It tested out properly.
However I do not remember the version of selenium server and firefox used.
Now after some issues, I had removed Ubuntu and intalled Mint on my system.
While testing the page, I get a lot of error messages and a blank firefox screen.
Current version of firefox is 30 and Selenium 2.4.2
Tried with firefox versions 25,26,27,30.
I have posted the codes below.
Any help will be appreciated.
Output of Selenium starting
java -jar selenium-server-standalone-2.42.2.jar25 Jun, 2014 3:36:17 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a standalone server
15:36:17.264 INFO - Java: Sun Microsystems Inc. 20.45-b01
15:36:17.264 INFO - OS: Linux 3.13.0-24-generic amd64
15:36:17.280 INFO - v2.42.2, with Core v2.42.2. Built from revision 6a6995d
15:36:17.347 INFO - Default driver org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{platform=WINDOWS, ensureCleanSession=true, browserName=internet explorer, version=}] does not match with current platform: LINUX
15:36:17.398 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
15:36:17.399 INFO - Version Jetty/5.1.x
15:36:17.400 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
15:36:17.401 INFO - Started HttpContext[/selenium-server,/selenium-server]
15:36:17.401 INFO - Started HttpContext[/,/]
15:36:17.419 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler#a39ab89
15:36:17.419 INFO - Started HttpContext[/wd,/wd]
15:36:17.422 INFO - Started SocketListener on 0.0.0.0:4444
15:36:17.422 INFO - Started org.openqa.jetty.jetty.Server#5abb7465
Output of Running a PHPUnit Test
phpunit testBooking.php
PHPUnit 3.7.28 by Sebastian Bergmann.
E
Time: 5.24 seconds, Memory: 3.00Mb
There was 1 error:
1) TestBookingBlockDate::testBlock
RuntimeException: POST /session/url
Build info: version: '2.42.2', revision: '6a6995d', time: '2014-06-03 17:42:03'
System info: host: 'Sworoop', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-24-generic', java.version: '1.6.0_45'
Driver info: driver.version: unknown
/var/www/Folder/UnitTests/TurningStone/testBooking.php:13
/var/www/Folder/UnitTests/TurningStone/testBooking.php:13
FAILURES!
Tests: 1, Assertions: 1, Errors: 1.
PHP Fatal error: Uncaught exception 'RuntimeException' with message 'DELETE /session
Build info: version: '2.42.2', revision: '6a6995d', time: '2014-06-03 17:42:03'
System info: host: 'Sworoop', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-24-generic', java.version: '1.6.0_45'
Driver info: driver.version: unknown' in /usr/share/php/PHPUnit/Extensions/Selenium2TestCase/Driver.php:127
Stack trace:
#0 /usr/share/php/PHPUnit/Extensions/Selenium2TestCase/Session.php(137): PHPUnit_Extensions_Selenium2TestCase_Driver->curl('DELETE', Object(PHPUnit_Extensions_Selenium2TestCase_URL))
#1 /usr/share/php/PHPUnit/Extensions/Selenium2TestCase/Session.php(117): PHPUnit_Extensions_Selenium2TestCase_Session->stop()
#2 [internal function]: PHPUnit_Extensions_Selenium2TestCase_Session->__destruct()
#3 {main}
thrown in /usr/share/php/PHPUnit/Extensions/Selenium2TestCase/Driver.php on line 127
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:46
PHP 3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:129
During this I get a blank firefox window which I have to manually close.
Solved it after reinstalling PHPUnit using composer instead of apt.
Thanks everyone :)