//*[@text="Pour moi"]Could you give an example of your xpath touch?
Developers said this has been fixed in version 2.3.3.0my transitory solution was to stop and start zennodroid when the problem occurs![]()
Downloaded from zennolab account panel?i use the 2.3.3.0
of course !Downloaded from zennolab account panel?
Ok, we will check itthe problem occurs with android 9
So, it works normally with android 7?for now, i downgrade to Android 7, when I start the next project with Android 9 I will send it to you.
In Android 7, Sometimes it lagging and when happen I wait 5-10 seconds and it works contrary to android 9So, it works normally with android 7?
It does not always find the element as far as I testedIn Android 9, Sometimes it lagging and when happen I wait 5-10 seconds and it works contrary to android 9
now the problem is in Android 7 !!!! updating tree element freeze or generate the error again. please provide any tips about it.It does not always find the element as far as I tested
element tree is updated untill the element is found,now the problem is in android 7 !!!! updating tree element freeze or generate error again. please any tips about it
yes 'am sure it's the "accept" button of the agreement rules in google chrome. As I said above, it was working smoothly until this brutal closeelement tree is updated until the element is found,
you sure the element always exists?
I guess the VM went broken after brutal closeyes 'am sure it's the "accept" button of the agreement rules in google chrome. As I said above, it was working smoothly until this brutal close