Wait for page load is sometimes unreliable. It doesn’t always do what we think it should, unfortunately. Especially with these kind of highly scripted web pages.
As I said before, use Check App State to wait for a known element to appear to confirm the page loaded. Heck, you could even just use the same button you’re trying to click as the object to confirm page load (assuming this button is the first thing you click). Just make sure to set a very long timeout because it appears this page takes a long time to load.
Take a notepad and copy the selector which is working. When the selector failing, copy the activity to different new sequence (Since I don’t want you to disturb your current logic) re indicate the same element. Copy this new selector to the notepad where the previous selector has already copied. Now, compare these two and see what is changing
after a long time, i have tried, simulate, hardware events,
as well, for the click button- but it again gives the same error, sometime it works, sometimes it does not, how to ensure that it clicks 100% eeverytime?
Anil_G
Ajay_Mishra
pravallikapaluri
postwick
AJ_Ask
Anonymouss
vignesh.maruthappan
mkankatala
mrohan.senapaty
ATHEEQ_UR-RAHMAN