I need to integrate my Dapp with Trust Wallet's internal DApp browser. I followed this instruction on the trust wallet website. However, when I run my DApp inside the trust wallet DApp browser, it shows a mobile tab with a connect button and when I press that button, the current web page simply redirects to google to search for WalletConnect standard URI, i.e. wc:00e46b69-d0cc-4b3e-b6a2-cee442f97188... (it seems that DApp browser does not understand that format).
Additionally, when I access my Dapp through a mobile browser such as Firefox on android, it opens the trust wallet and connects to it successfully, but no further transactions are getting shown on the wallet to confirm. Only on the desktop browsers everything works smoothly (when I connect through QR code).
Is there any special consideration or requirement to integrate a Dapp with trust wallet internal browser?
TrustWallet – How to Use TrustWallet DApp Browser with WalletConnect
dapp-developmentdappstrusttrustwalletwalletconnect
Related Solutions
I'm not sure if you are describing the dataflow rather than the actual system architecture, but if you are it isn't entirely correct.
Overview of decentralised applications:
Alex Van de Sande wrote a great article on building serverless applications and in it he contrasts the distinction between a centralised build and a decentralised build.
https://blog.ethereum.org/2016/07/12/build-server-less-applications-mist/
Traditional Centralised Structure
New Generation Decentralised Structure
The article talks a lot about Mist, but this was when Mist really was the only shown in town. Now we have Parity and even MetaMask that allow users access to web3.js and a connection to the an Ethereum wallet, and importantly the ability to use the Ethereum wallet to sign transactions on the Ethereum blockchain/ network.
Considering your example:
[Web Browser (end user)] <==> [Server (web application/javascript <==> web3 <==> ethereum client)] <==> [Ethereum Network (solidity code)]
The Ethereum client isn't usually on the server side, there are exceptions like the case of using something like MetaMask, but in that case you'd use MetaMasks serverside and not your own. The Ethereum client would be part of the web browser. Also the client is what communicates with the Ethereum Network, not your server. So your structure / relationship would need to be split into two parts and look more like:
Downloading the HTML and JS:
[Web Browser (end user <==> Ethereum client)] <==> [Server (web application/JavaJcript <==> web3)]
Interacting with the blockchain:
[Web Browser (end user <==> Ethereum client)] <==> [Ethereum Network (solidity code)]
See here:
Any DeFi application must choose what wallets they support. Developers must add support for different wallet protocols. Besides mobile wallets, there are plenty of other wallet options. The most popular way to connect a mobile wallet is WalletConnect.
Best Answer
It seems that the problem was brought about by the Trust wallet itself and after upgrading to the latest version (4.9 on android), the issue is now solved and everything works as expected.