Hi there,
I have just started to use UiPath to check its functionality, so that i can include in our enterprise products.
I created a Xamarin Forms app (basic) and tested in Samsung tablet physical device. The app works fine. Installed Appium and Installed UIAutomator2 Plugin.
I have added a device and app in mobile Device Manager window.
The inputs provided were ::
Started appium from CLI
C:\windows\system32>appium --base-path=/wd/hub
[Appium] Welcome to Appium v2.0.0-beta.66
[Appium] Non-default server args:
[Appium] {
[Appium] basePath: ‘/wd/hub’
[Appium] }
Appium Url :: http://localhost:4723/wd/hub
appium:automationName : UIAutomator2
While running app in Mobile automation window,
It threw →
[WD Proxy] Got response with status 500: {“sessionId”:“eb974336-f582-44a7-94e9-b95db7523180”,“value”:{“error”:“unknown error”,“message”:“Timed out after 15541ms waiting for the root AccessibilityNodeInfo in the active window. Make sure the active window is not constantly hogging the main UI thread (e.g. the application is being idle long enough), so the accessibility manager could do its work”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.UiAutomator2Exception: Timed out after 15541ms waiting for the root AccessibilityNodeInfo in the active window. Make sure the active window is not constantly hogging the main UI thread (e.g. the application is being idle long enough).
I couldn’t find relevant thread in UiPath. Can someone suggest a solution for this. Better, if there is any working sample for UiPath with apps created using Xamarin Forms, it would be great [I saw threads that say UiPath not working with Xamarin Forms ]. Any pointers would be helpful.
Thanks in Advance.
Regards,
Naga