You can start with this information:
DYLD 4 Symbol missing Symbol not found: _$s11DappBrowser27WalletConnectCryptoProviderC0cD6Signer0eF0AadEP9keccak256y10Foundation4DataVAJFTW
That's a mangled symbol name, which is a normal complier transformation to encode information about the symbol. Let's make that a bit more readable with some command line foo:
% xcrun swift-demangle s11DappBrowser27WalletConnectCryptoProviderC0cD6Signer0eF0AadEP9keccak256y10Foundation4DataVAJFTW
[...] protocol witness for WalletConnectSigner.CryptoProvider.keccak256(Foundation.Data) ->
Foundation.Data in conformance DappBrowser.WalletConnectCryptoProvider : WalletConnectSigner.CryptoProvider in DappBrowser
I trimmed and reformatted the output so it's a bit clearer for this thread. If you extract these types and protocols from your app and place them into a test project configured with the same deployment target as your real app, do you see the same crash signature? That will help narrow down if this is an issue specific to your project in its entirety, or something that is more broadly reproducible, which will help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project.
— Ed Ford, DTS Engineer