Hello,
Testing manually the website "https://www.smiles.com.br/home" in any mobile browser, elements are working really fine as desktop browsers, but when I try to use in Ranorex mobile browser (I need automate with ranorex mobile browser), elements aren't working.
Below, two images comparing behavior between Safari and Ranorex.
I'm using IOS 10.0.2 with Ranorex Service 2.2.0 and RxAutomation v2.2.0.
Regards,
Wellington Santana
Ranorex Web Browser is not working like other browsers
-
wellingtonsantana
- Certified Professional
- Posts: 18
- Joined: Sat Jan 23, 2016 12:50 am
- Contact:
Ranorex Web Browser is not working like other browsers
- Attachments
-
- Some error that often appears
- B36EA9D5-1C53-4B52-BABA-321159DCFFB3.jpg (39.88 KiB) Viewed 1113 times
-
- Behavior in Ranorex mobile Browser
- 63379A7C-DDD0-4E76-A3BD-6C706E79E958.jpg (74.44 KiB) Viewed 1113 times
-
- Behavior in others mobile browsers
- 5DC87F46-F349-4675-A893-4B8190245656.jpg (68.46 KiB) Viewed 1113 times
-
Support Team
- Site Admin
- Posts: 12169
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: Ranorex Web Browser is not working like other browsers
Hello Wellington Santana,
Thank you for reporting the issue.
It seems the error pops up when an asynchronous load is canceled. Safari and other browsers hide these type of errors. The Ranorex mobile Browser shows the error in the browser directly.
I found a description for this error message on the website developers.apple.com:
https://developer.apple.com/library/mac ... -CH3g-SW40
I already added an item into our bug tracking system. Unfortunately, there is no workaround at the moment.
Regards,
Bernhard
Thank you for reporting the issue.
It seems the error pops up when an asynchronous load is canceled. Safari and other browsers hide these type of errors. The Ranorex mobile Browser shows the error in the browser directly.
I found a description for this error message on the website developers.apple.com:
https://developer.apple.com/library/mac ... -CH3g-SW40
I already added an item into our bug tracking system. Unfortunately, there is no workaround at the moment.
Regards,
Bernhard
