Browse Deeplink Override Behavior

[jassuwu]

I am currently working on a dApp that integrates multiple wallets to support a bridge-like feature. The primary functionality of the dApp operates on the Base mainnet, and it uses the Thirdweb smart wallet (AA) for wallet connections. We are also in the process of adding a token swap functionality to enable deposits from various chains.

As part of this update, we are exploring adding support for the Solana network, and having Phantom Wallet functionality work smoothly would be a significant benefit.

I am encountering an issue when attempting to connect Phantom Wallet on mobile via the Dynamic.xyz widget. Here’s the flow:

1. When connecting to the Base mainnet using MetaMask on mobile Chrome using Thirdweb, the connection process works as expected. Redirect to the app to sign, after signing the signature, the app auto-redirects to the Chrome browser to continue the session.

2. However, when trying to connect to Phantom Wallet using the Dynamic.xyz widget, the app opens within Phantom’s in-app browser instead of staying within the Chrome browser. This behavior is causing conflicts, particularly with thirdweb’s social login integration and other wallet login functionalities.

I've looked into the docs to see that this is because of the Browse deeplink feature. Now the above issue could be a Dynamic.xyz thing, but I'm asking here just in case. I’m looking for guidance on how to manage or override this behavior to ensure seamless wallet interactions across platforms.

[adamdelphantom]

Hey @jassuwu, I'm not familiar enough with dynamic to know if it's possible to override the use of the browse deeplink. My only guidance would be to use the supported phantom native deeplink method's. I think it's worth checking with dynamic to see if they enable this functionality.

[jassuwu]

Thanks for reply. Looks like it's upto the aggregator to provide the choice and management of deepking behavior. I've found this in the dynamic.xyz docs. This should be what I was looking for. I'll close this discussion for now.

[jassuwu]

Add-on: @adamdelphantom I've had to reopen the discussion, hoping it’ll get seen. This is my continued conversation with Dynamic.xyz.

Here's the link to the ongoing chat for context.

To summarize:
After getting the "redirect" behavior to work instead of the default "in-app-browser", I've noticed that this behavior is not working like it's supposed to.

The flow should be
Click connect in dApp ---redirect---> Sign in App ---redirect---> connected
But for Phantom wallet, it's
Click connect in dApp ---redirect---> Sign in App --- redirect to new tab ---> connected

This causes loss of state in the app. Was facing this in our app. But was able to reproduce this even with https://go.dynamic.xyz/4hbFS9C on mobile browser.

Dynamic has mentioned that this behavior is something they can’t control due to Phantom’s handling of the deep linking, and I’m hoping to get further insights from you on how we might mitigate this or if there’s a way to better manage the flow to avoid the tab opening behavior.

Thanks in advance.