When I use GeckoFx-45 I sometimes get a MsgBox popup named "Alert" with the text:
The operation timed out when attempting to contact xxx
I can't find a option to disabled this alert.
It needs to manually clicked to resume the Application.
Does anybody knows how to disabled the Timeout Alert at GeckoFx-45 Browser?
Thank You
Related
I'm trying to figure out why voice over seems to be interrupting an alert role on a webview. I'm on iOS 15.3 and starting an ASWebAuthenticationSession.
If an error occurs during log in such as, Username and Password are not recognized an error would appear on the html.
<div id="authn-error" name="authn-error" role="alert">
$templateMessages.getMessage($authnMessageKey)
</div>
If all goes well VO reads out the error message but, sometimes it gets interrupted with the address bar.
When the page is loading the voice over moves to the error then shifts focus back to address bar and reads out the "Address ten percent someWebSite.com secure and validated".
Any help is appreciated.
So I'm attempting to implement touchID in my app, but when I get a mismatch the standard alert for retry pops up. Clicking "Enter Password" does nothing (maybe because I'm on the simulator).
I'm wondering if it's possible to customize the options on that alert, maybe hide "Enter Password" so we can just leave cancel or retry as the only options for this scenario.
Currently I'm only handling success, and am unsure yet how to handle the failure case (i.e. what I can do in the else statement that goes with if success
Documentation seems to be purposely vague on the issue of how to actually handle failures.
Found it through experimentation. LAContext's localizedFallbackTitle holds the answer. It may default to "Enter Password" but setting it to an Empty String hides the button. Wish the documentation would have been more clear on that.
I am implementing apply pay with stripe. When I clicked a button it doesn't show the proceed to pay page and it shows an error like
"Failed to present in-app payment interface: Error Domain=PKPassKitErrorDomain Code=-1"
Cannot Present Remote Interface of type: PDRemoteInterfaceTypeInAppPayment
and Connection to remote alert view service failed.
How to solve that error.what's that meaning of the error PassbookUiService error
I'm working on retrieving steps data within HealthKit. The query all works as expected (I'm only retrieving step data) however I'm having a strange issue with the Health Access modal that appears (see screenshot below - this is NOT my app, just an example screenshot taken from the web)
The issue is when the user soft closes the app (i.e. pressing the home to get to springboard) and then goes back into the app. The modal doesn't want to disappear when clicking allow or disallow.
Looking at the log it appears I have this strange error:
Error Domain=com.apple.healthkit Code=5 "(null)"
Any thoughts? If further info is required please let me know.
P.S. Just an addition to this, I notice that when clicking "Don't Allow" (where the "Cancel" is within the screenshot), I get an alert dialogue stating:
"You can turn on health data categories later in the Health app."
Upon clicking "OK" the Health Access screen still does not dismiss.
P.S.S. Not sure if this affect this but when the Health Access screen appears, it does so with the following message in the Log:
Unbalanced calls to begin/end appearance transitions for <UIViewController: 0x1343f4040>.
currently I am using following method to read the alert message content but it throws error saying not yet implemented. What is the alternative method to achieve this?
driver1.switchTo().alert().getText();
Error :org.openqa.selenium.WebDriverException: Not yet implemented. Please help us: http://appium.io/get-involved.html (WARNING: The server did not provide any stacktrace information)
In appium there is no need to use the switchto.alert method to capture the alert messages. Alert messages in mobile are actually in the native context and you have to switch to the native context to access the alert buttons/text.
driver1.context("NATIVE_APP");
After that you can capture the alert as an native element and fire any action upon it. Ex :
driver1.findElement(By.xpath("//android.widget.Button[#text='Yes']")).click();