Open Deep Link – MagicPod Help Center

In mobile app testing, the "Open deep link" command is available. This command enables the following operations:

App to Be Opened with the Link

Which app opened with the specified URI as a deep link depends on the following factors:

The Behavior Based on Settings:

If a specific app is set in the "App to be opened with link" option, that app will take priority.
If "Not specified" is selected, the system's default app associated with the link is typically used.

In external cloud environments (e.g., BrowserStack, SauceLabs), the "Not specified" option for the "App to be opened with link" option is not supported.
Attempting to use the "Not specified" option will result in an execution error.
To avoid errors, set a specific app in the "App to be opened with link" option when using these environments.

Chrome may display a "Welcome screen" or a "Sign-in prompt" upon launch. These can be dismissed using the "Tap" command if necessary.
A bug has been reported where a WebView scan may fail if an empty tab exists in Chrome. This can occur because Chrome may automatically create an empty tab upon launch. Consider closing empty tabs using the "Tap" command if necessary.
- For more details, refer to "Known issues with Android WebView" in "Testing WebView."

In environments with iOS 16.3 or earlier or Xcode 14.2 or earlier, links are opened via Safari internally before being redirected to the associated app. This behavior introduces the following restrictions:
- If a tab is already opened, Safari might overwrite an existing tab.
- It is not possible to set a specific app to open links. As a result, the "App to be opened with link" option is not applied.
- If there are typos or errors in the specified URI, Safari may display it as a search query instead of displaying an error.