Search found 8 matches
- Thu May 09, 2019 7:56 pm
- Forum: General Questions
- Topic: @childindex issue after upgrading to 9.0.1
- Replies: 3
- Views: 1169
Re: @childindex issue after upgrading to 9.0.1
Thank you. I opened a ticket by email with the log and snapshop.
- Thu May 09, 2019 2:29 pm
- Forum: General Questions
- Topic: @childindex issue after upgrading to 9.0.1
- Replies: 3
- Views: 1169
@childindex issue after upgrading to 9.0.1
Hello, We upgrade from 8.2 to 9.0.1 and we encountered problems with the @childindex in our paths. Note: We had NO issues since 6.x with using ChildIndex. So now we have many scripts that fails after the upgrade to 9.0.1 The path looks like this - See attached zip file with image1.jpg With that we c...
- Thu May 02, 2019 8:17 pm
- Forum: General Questions
- Topic: Bug in 9.0.1? (after upgrading from 8.2): @innertext~
- Replies: 3
- Views: 1106
Re: Bug in 9.0.1? (after upgrading from 8.2): @innertext~
Not quite sure I understand your response. With version 8.2 I was using this: a[@innertext~'Auto'] This was working fine to get the first item in the table. I upgraded to Ranorex 9.0.1, and the script got upgraded with no errors 1 It now fails and it does not work anymore . Because it cannot find th...
- Thu May 02, 2019 6:26 pm
- Forum: General Questions
- Topic: Bug in 9.0.1? (after upgrading from 8.2): @innertext~
- Replies: 3
- Views: 1106
Bug in 9.0.1? (after upgrading from 8.2): @innertext~
Hello, Many of our scripts do not work anymore after upgrading from 8.2 to 9.0.1. Example: Version 8.2 (Working): //tbody[#'tbody_l_com_gateway_domain_Terminal']//a[@innertext~'Auto'] In 9.0.1 not working anymore If I track the object I have this: //tbody[#'tbody_l_com_gateway_domain_Terminal']//a[@...
- Thu May 02, 2019 5:51 pm
- Forum: Bug Reports
- Topic: Element.ChildIndex does not work with JS-based RanoreXPath evaluation.
- Replies: 6
- Views: 2092
Re: Element.ChildIndex does not work with JS-based RanoreXPath evaluation.
Hello,
I have the same issue. 40% of our scripts use childindex (they were working with 8.2)
You have a timeline when this is going to be fixed?
Thank you
I have the same issue. 40% of our scripts use childindex (they were working with 8.2)
You have a timeline when this is going to be fixed?
Thank you
- Tue Apr 30, 2019 7:53 pm
- Forum: General Questions
- Topic: RX license is not available, waiting... after upgrading to 9.0.1
- Replies: 2
- Views: 1079
Re: RX license is not available, waiting... after upgrading to 9.0.1
Thank you very much.
That was the problem. Our IT team did not update the license.
That was the problem. Our IT team did not update the license.
- Thu Apr 25, 2019 2:42 pm
- Forum: General Questions
- Topic: RX license is not available, waiting... after upgrading form 8.2 to 9.0.1
- Replies: 1
- Views: 1034
RX license is not available, waiting... after upgrading form 8.2 to 9.0.1
Hello, I just upgraded the node locked machine from 8.2 to 9.0.1 I upgraded and compiled 1 script. I copied the new EXE to my runtime machine which was also upgraded from 8.2 to 9.0.1 When I run the EXE on my runtime machine I get this message RX license is not available, waiting... My license manag...
- Thu Apr 25, 2019 2:26 pm
- Forum: General Questions
- Topic: RX license is not available, waiting... after upgrading to 9.0.1
- Replies: 2
- Views: 1079
RX license is not available, waiting... after upgrading to 9.0.1
Hello, I upgraded the locked node from 8.2 to 9.0.1 as well as the scripts on that machine. I copied the updated compiled script (EXE) to my Runtime machine, which also been upgraded from 8.2 to 9.0.1 When I start a script on the runtime machine I get : RX license is not available, waiting... I have...