Questions

We are experiencing an issue where clicking a verified deep link successfully opens our native Median app, but instead of routing the webview to the specific target path, the app consistently drops the user onto the configured Initial URL (the homepage).

This happens on both cold starts (app closed completely) and warm starts (app already running in the background).

Here are our configuration details:

• Link Behavior Regex Rule: https?://.yourdomain.com/. set to Internal
• Universal/Deep Links: Configured with broad wildcards ("paths": ["*"] / handle_all_urls) for our domain.

What we have verified:

• The OS successfully hands off the action to the app (the app opens immediately upon tapping the link, so the AASA / Assetlinks files are verified and working).
• The URL works flawlessly on standard mobile browsers (no server-side or backend redirects are throwing the user to the homepage).
• The behavior persists during a warm start, meaning the app comes to the foreground but fails to update the active WebView window with the new path payload.

Has anyone encountered this where the native wrapper drops/ignoring the incoming path parameter upon link interception and forces a navigation back to the initial root URL? Is there an appConfig.json navigation property or a deep-link update behavior setting we need to adjust to ensure the active WebView correctly navigates to the incoming URL?

Thank you!