Handle iOS deep link alert?

[paulaladdin]

Hello, I'm an automation engineer at Lyft trying to automate testing deep links in iOS. I've managed to get everything working up until the point where we must accept the iOS alert dialog (picture attached).

The issue is that:

--Appium hangs indefinitely on info: [debug] Sending command to instruments: au.mainApp().getTreeForXML(). (Eventually triggers session timeout)

--Trying to refresh Appium Inspector when this alert dialog is up also results in an indefinite hang.

--Searching for any page elements results also in an indefinite hang

--Attempting to tap by coordinates also results in an indefinite hang.

After researching this issue online, I tried adding these values to my desired capabilities:

autoAcceptAlerts: true,
waitForAppScript: true

But they had no practical effect.

We've already invested a significant amount of effort into making this work and have had success on Android, and this seems to the be the only issue still blocking us on iOS. Any help or insight would be greatly appreciated.

Full log attached. FYI we're using the Python bindings.

appiumlog.txt

[imurchie]

Do you have a way for us to reproduce this? It would be helpful to try to diagnose. Thanks!

[paulaladdin]

Sure, essentially the code I'm using to test this does the following:

• Open an Appium session with your app under test
• Background the app, open up safari
• Load a URL for a page that contains a deep link.
• Have appium click on a deep link.
• Open and close the bookmarks page (this is apparently an iOS bug).
• At that point, this alert dialog appears.

A couple of caveats:

• The deep link must be a JS button that calls window.open() on the link (I haven't been able to get it work with a standard <a href=> style link)
• Make sure to switch between native_app and webview contexts as needed.

Let me know if you have any further questions.

[paulaladdin]

Any update on this? We're anxious to find a resolution or workaround; again, this is the only issue blocking complete rollout of this test.

[imurchie]

I haven't had a chance to try to reproduce, in order to try to find a solution.

[imurchie]

I can't reproduce this. Mostly because I'm not sure how you get from step 1 to step 2. Something is not working as it should in your set up, because when background returns the app ought to be in the foreground again, and clicking on the safari button ought to be impossible.

[sandykaka]

@paulaladdin did you find work around for this problem?

[sandykaka]

@imurchie I'm facing the same problem, any solution for this?

[KazuCocoa]

As the comment on #121 (comment) and Alert window from browser not accessible to driver for iOS appium/appium#6702 , close this issue on here.

[liangway]

Blocked by this too, any solution?