Ranorex Studio, Spy, Recorder, and Driver.
-
tiffin.filion
- Posts: 56
- Joined: Thu Oct 29, 2020 12:47 am
Post
by tiffin.filion » Wed Aug 03, 2022 10:58 pm
I'm wondering if Ranorex Studio 10.2.4 doesn't actually work on Windows 11?
My tests worked fine when I was running 10.1.4 while on Windows 10, but now the Close application action fails. I even created a sample test using the Solution wizard and I still get the same thing.
Code: Select all
Action 'close' failed on element '{WebDocument:Automated GUI Testing Tools}'.
Index was outside the bounds of the array.
-
tiffin.filion
- Posts: 56
- Joined: Thu Oct 29, 2020 12:47 am
Post
by tiffin.filion » Wed Aug 03, 2022 11:38 pm
I should note, if I run a test through BrowserStack and select Windows 11/Chrome, it works fine. It's just my machine where something is broken.
-
tiffin.filion
- Posts: 56
- Joined: Thu Oct 29, 2020 12:47 am
Post
by tiffin.filion » Fri Aug 05, 2022 8:25 pm
Did some testing with older versions of ranorex:
10.1.7 & 10.2.2 I have no issues with Close application.
10.2.3 & 10.2.4 I get the index outside of bounds error message.
-
tiffin.filion
- Posts: 56
- Joined: Thu Oct 29, 2020 12:47 am
Post
by tiffin.filion » Fri Aug 12, 2022 6:08 pm
An update, Ranorex Support was able to reproduce so it's an issue with the newer versions of Ranorex running on Windows 11. Just FYI.
-
dhale
- Posts: 84
- Joined: Thu Feb 27, 2014 7:33 pm
Post
by dhale » Mon Aug 15, 2022 4:28 pm
Thanks for this post - I came across it while searching to see if anyone else was having similar issue.
I am on Win10 / Edge.
For now, I am going to switch it up a bit and do .Browser.Close() to work around the issue
-
ddweber
- Posts: 13
- Joined: Wed Sep 04, 2019 10:13 am
Post
by ddweber » Fri Aug 19, 2022 1:06 pm
We are experiencing the exact same issue with version 10.2.4 on
Windows 10. It seems that the
close grace period of this action is the problem. With its default value of 0ms the exception gets thrown. With any value greater e.g. 1ms the issue seems to be gone.
The issue also effects the actions in the context menu of the spy tool...
Working around the issue in all our test projects is not an option. I hope that this basic functionallity is fixed in the next release
-
gochi88
- Posts: 2
- Joined: Wed Sep 01, 2021 6:47 pm
Post
by gochi88 » Mon Aug 22, 2022 6:17 pm
I'm also facing same problem
, but after re install it's not happed with me.
-
dhale
- Posts: 84
- Joined: Thu Feb 27, 2014 7:33 pm
Post
by dhale » Tue Aug 23, 2022 4:06 pm
I have submitted a support request regarding this issue asking for resolution.
-
tiffin.filion
- Posts: 56
- Joined: Thu Oct 29, 2020 12:47 am
Post
by tiffin.filion » Tue Aug 23, 2022 5:53 pm
dhale wrote: ↑Tue Aug 23, 2022 4:06 pm
I have submitted a support request regarding this issue asking for resolution.
I have as well. I emailed first week in August and they replied that they were able to replicate the issue and would let me know if there were any workarounds for it. But that was 2 weeks ago and haven't heard anything since. Going down to 10.2.2 has worked for us, and I saw another user just used code as a work around. But yah, we shouldn't have to figure out a way to make basic functionality, like closing a browser, work.
-
Stub
- Posts: 515
- Joined: Fri Jul 15, 2016 1:35 pm
Post
by Stub » Wed Aug 24, 2022 8:29 am
I've been waiting since about June 6th for a resolution to my Ranorex-introduced issue. Utter silence from Ranorex on it. We're stuck with Ranorex v10.1.7!
-
KaiF
- Posts: 4
- Joined: Fri Oct 01, 2021 8:35 am
Post
by KaiF » Thu Aug 25, 2022 7:54 am
ddweber wrote: ↑Fri Aug 19, 2022 1:06 pm
...With its default value of 0ms the exception gets thrown. With any value greater e.g. 1ms the issue seems to be gone ...
Thank you,
this tip was very helpful!
-
ddweber
- Posts: 13
- Joined: Wed Sep 04, 2019 10:13 am
Post
by ddweber » Wed Oct 05, 2022 1:50 pm
This bug seems to be
fixed in
Ranorex 10.3.0