Jonathan Lipps
Jonathan Lipps
Thanks @NyCodeGHG. What's the mechanism by which you brought these fields back into package-lock?
Yes, we would like Appium to work as a grid 4 node in the future, but currently it does not do that. For now, use the strategy described [here](https://appium.github.io/appium/docs/en/latest/guides/grid/)
at the recent selenium+appium summit we did identify this as a convenient way to help the projects integrate. it probably would look the maintenance and documentation of a grid node...
> What did we get working at the summit Grid wasn't a target for work at the summit, so nothing > what still needs to be done My idea was...
should probably also be supported in 1.5, since the watch is basically out now...
no ETA at the moment
The element you're trying to get the text of is an alert? Alerts are typically native elements (not webview ones), so I would work with the alert in the native...
OK, the error appears to be happening when Appium is checking whether an alert is obscuring the webview. @mykola-mokhnach can you tell whether this error is coming from WDA or...
@mykola-mokhnach are you sure? ``` [debug] [XCUITestDriver@0aa1 (57002fb2)] Proxying [GET /alert/text] to [GET http://127.0.0.1:8100/session/D4D39557-3ABC-4DCE-9656-687C3C9741BC/alert/text] with no body ``` This looks like it's being proxied to WDA
thanks @ilendemli a repro is useful. the investigation/solution might take some time as there is a lot of updating work that needs to be done on the remote debugger code...