You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently preventing us from running our automation against an iOS device with its language being set to Simplified Chinese and Traditional Chinse...so it is urgent for us....hopefully can hear back from you soon
The text was updated successfully, but these errors were encountered:
Thanks for your promptly response Jmoody...I can clearly see the zh_TW (Traditional Chinese) and zh_CN (Simplified Chinese) alerts files and the alert definitions we need in those files, e.g: Bluetooth permission...
{
"title": "“%@”想要使用蓝牙",
"buttons": [
"好"
],
"shouldAccept": true
}
Not sure why DeviceAgent/Xamarin.UITest is not dismissing the springboard alert still? I am using Xamarin.UITest 3.0.7...Can you think of anything where this issue could occur?
Bluetooth Alerts are difficult to test. We cannot reliably generate them and the text on devices and simulators is often different which makes matching difficult.
You will probably need to manage these alerts manually.
You are using Xamarin.UITest? If so, you will need to make a few HTTP requests to the DeviceAgent. I don't think Xamarin.UITest has an API for this - maybe it does.
Turn off automatic dismissal of SpringBoard alerts - otherwise, you will see an exception
Trigger the alert
Handle the alert by touching the correct button
Optionally turn on automatic dismissal of SpringBoard alerts
I know that DeviceAgent is not open source yet but is there a way for me to quickly add the Simplified and Traditional Sprintboard alert definitions into here:
https://github.com/calabash/DeviceAgent.iOS/blob/b6ac427308ed5b4a58ddc7011d04ccc13754f707/Server/Utilities/SpringBoardAlerts.m#L107
It is currently preventing us from running our automation against an iOS device with its language being set to Simplified Chinese and Traditional Chinse...so it is urgent for us....hopefully can hear back from you soon
The text was updated successfully, but these errors were encountered: