Run all tests unattended in a suite after errors occur on Android
- 7 years ago
In my case, it was code that replaced your line for finding the Operatorbutton. We called it "ActivateForm". Basically, we would pass into it the form name of the expected "next" form that we were expecting to see. We then executed a bunch of code that was unique to our situation.
Generally, you're going to want a common method that you're going to be able to call anywhere that, upon going to a form or attempting to get a component or whatever the situation may be, you call that code before you attempt any actions against the component to do a "sanity" check to make sure that things are ready for interaction. It's going to be unique to what you're doing.
To be honest... if this Alert keeps coming up, rather than trying to write a bunch of code to handle it, I'd want to figure out why the Alert keeps coming up and figure out what can be done to prevent it.