-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Slowness on app launch #998
Comments
Same observed here #993 (this is a duplicate) |
Also for me this is true if WDA was compiled with Xcode 10. If I compile WDA with Xcode 9.4.1, and then run tests on iOS 11.4 and iOS 12.0 Simulators, then it is as fast as 5-6 seconds on application start. @andrecnogueira can you try WDA binary compiled with Xcode 9.4.1 ? |
I tried with a pre built WDA, compiled with Xcode 9.4.1, and I still see the issue.
I noticed this issue when I migrated from Appium 1.7.2 to 1.9.X. when we have been forced to update drivers to start building with Xcode 10. I will see if I can use the WebDriverAgent packed with Appium 1.7.2 as a pre built WDA and let you know. Not sure if it will be compatible tho. |
@fr0l , As I promised I build WDA version that comes packed with Appium 1.7.2 built with xcode 9.4.1 and it worked just fine...I did not see such long time on app launch. Again, I noticed such slowness when I upgraded from Appium 1.7.2 to 1.8.0. I am not sure what has changed on WDA side making the long application start. Snippet logs for the above setup
Appium logs pre build wda compiled with Xcode 9.4.1 |
I'm seeing similar issues using appium 1.9.2-beta.2. I have Xcode 10 installed on the computer and I have set waitForQuiescence to false in my capabilities. My tests start, app is installed on the simulator and then it sits there for a minute or two before anything happens. This didn't happen when I started using appium with version 1.7.2 with corresponds to what @andrecnogueira is telling. |
I am also facing this issue and our execution time is increased drastically. Can anyone please look into this issue? |
@fr0l I was wondering if there is any way to prioritise/bring more attention to this issue as building WDA with 9.4.1 is not an option to us as our major tests are running on iOS 12 where Xcode 10 is required. |
I am facing the same issue with the slowness of launching the app and finding the elements with Appium in iOS. I am also using Appium 1.9.1 with Xcode 10 As an idea, the appium looks for an element which is not present for approx 20 times before it moves further which is making it extremely slow. For finding elements, I am either relying on accessibility ids wherever I have access to those other wise I am using this approach |
Is #1013 a duplicate of this? |
Should be resolved, pls reopen otherwise |
@marekcirkos I just write comment in #999. Seems problem still here. |
I still see this problem as well . As soon as we launch appium takes 6 to 9 minutes to execute tests Enqueue Failure: Failure fetching attributes for Device system-wide element: Error Domain=com.apple.XCTestErrorDomain Code=1000 "Timeout waiting for fulfillment of promise for 'Fetching attributes for Device system-wide element'." UserInfo={NSLocalizedDescription=Timeout waiting for fulfillment of promise for 'Fetching attributes for Device system-wide element'.} |
With Xcode10 release I noticed our build execution time increased significantly, when checking Appium logs with showXcodeLog=true, I see WDA gets stuck waiting for accessibility to load and then it throws Enqueue Failure. I am not sure which accessibility WDA is looking for. Please, can anyone look into it?
Fuller logs
Env:
Xcode 10
iOS version: 11.4 and 12
Simulators: any
WDA Version: latest checkout from master
The text was updated successfully, but these errors were encountered: