-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Enqueue Failure: Failure to determine system application: (null) #1013
Comments
I've the same issue, but in my case it's with a specific project. (I checked with other apps looking if I missed some config. but they're run fine) |
I have same issue but only then I use appium screen recording. appium: 1.9.1 |
This seems to be remedied a bit by using My setup We would be really thankful if this could be tackled in a timely manner. Please also let me know if somebody has other workable workarounds (except waiting 8-10 minutes ;-) per startup) |
In case anyone is still having the same problem, try upgrading everything (NPM, Appium, etc); I know it sounds obvious, but what's probably happened is that you've installed an OS upgrade that's not compatible with some component of the Appium/WebDriver setup. For me, the problem was carthage (brew update carthage) - an easy one to overlook. Hope this helps. |
I have the same issue on my pretty freshly installed MacOS and latest apps. Capability useNewWDA is set to true and I can see in Appium log it is really set and used. My app is installed and started by appium also the webrdriver app is installed but my selenium Python test doesn't start to run as it times out on the application determination. |
I feel like this issue is not bringing enough attention to it. (Almost 2 months old, same as others related to this) |
Hi guys, Sometimes works sometimes not. Eventually this issue keeps appearing and fixing it is tedious. |
I have also encountered this problem - I played with timeout values but found that |
I have the same problem. After opening the application, wda errors appear and the autotest does not start for a very long time. Environment Details: Appium log: Capability: I need help. |
@LilySmol, try increasing that wdaEventloopIdleDelay capability. I've noticed that in my case 3 seconds are not enough, so I have it set to 5. |
@nenaddrop, thank you, wda error was gone, but the run is still very slow. |
@LilySmol try setting the useNewWDA to false. If you are running multiple test scenario, this can increase the overall time of execution since WDA is getting re-installed for every new test. In what way are you experiencing the slowness? |
@nenaddrop, I set the useNewWDA to false and added capabilities.setCapability("noReset", true). Driver initialization reduced to four minutes. I get a message when I initialize the driver: |
This is happening because the appium server is trying to get the status from the WebDriverAgentRunner app that gets installed on your simulator, but the app might not be installed/running yet. If you want to make sure all is good, I would advise a re-install of the appium server (latest stable version) from npm (so that latest WebDriverAgent is installed alongside it) and remove the existing WDA app from your simulator (so a new fresh app can be installed). 4 minutes is still an awful lot. |
Hi, I am also facing the issue when I try to execute scripts on iOS real devices Error: Enqueue Failure: Failure getting list of active applications: Error Domain=com.apple.dt.XCTest.XCTFuture Code=1000 "Timeout waiting for fulfillment of promise for 'Fetching attributes 'XC_kAXXCAttributeFocusedApplications' for (null)'." UserInfo={NSLocalizedDescription=Timeout waiting for fulfillment of promise for 'Fetching attributes 'XC_kAXXCAttributeFocusedApplications' for (null)'.} /Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/WebDriverAgentRunner/UITestingUITests.m 37 1 Environment Details: My Capabilities: capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "iphone7-test"); It's taken almost 6 mins to start the execution. Please let me know anyone is there is any solution for this. |
Hi, I am also getting below error WebDriverAgentRunner-Runner[1861:65036] Enqueue Failure: Failure fetching attributes for (null): Error Domain=com.apple.XCTestErrorDomain Code=1000 "Timeout waiting for fulfillment of promise for 'Fetching attributes for (null)'." UserInfo={NSLocalizedDescription=Timeout waiting for fulfillment of promise for 'Fetching attributes for (null)'.} /Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/WebDriverAgentRunner/UITestingUITests.m Environment Details: Capabilities: |
Environment Details :
Capabilities: Comments
I face the same problem and really struck with this issue for more than 3 days .. Please let me know the solution |
Hello, after a long time without working with the ios automation, I tried again after my team made a change in the Splash/video and it was faster than the previous one and even that I saw in another forum this recommendation. so I'd like to recommend trying to verify your splash or make an updated. |
I discovered the problem could be old version of WebDriverAgentRunner. I was using WebDriverAgentRunner in appium 1.9.1 which has significant delay at launch. After switching to WebDriverAgentRunner in appium 1.13.0 everything runs smoothly. No need to set waitForQuiescence to false. |
this worked for me, thanks |
Hi Team,
I have upgraded Mac os and appium version and now I am getting following error.
Environment Details:
WebDriver.log
@beta version also)
The log is attached here
Update::
If I wait for 8 to 10 minutes then Execution start. Also noted that if WebDriverAgentRunner starts in background first time then execution start immediately. Now, if I start again without any change, it takes 8 to 10 minutes to start.
Observation is if I don't want to 8 to 10 minutes then I have to kill WebDriverAgentRunner from the background and start execution.
The text was updated successfully, but these errors were encountered: